EngineeringConnection Comparison Table

Entity > Physical > Object > SelfConnectedObject > CorpuscularObject > Artifact > EngineeringElement > EngineeringComponent > EngineeringConnection

Up: EngineeringComponent

EngineeringConnection comparison table

Subject documentation is a kind of be first domain of have axiom

EngineeringComponent A fundamental concept that applies in many engineering domains. An EngineeringComponent is an EngineeringElement that is a physically whole object, such as one might see listed as standard parts in a catalog. The main difference betweeen EngineeringComponents and arbitrary globs of matter is that EngineeringComponents are object-like in a modeling sense. Thus, an EngineeringComponent is not an arbtrary subregion, but a part of a system with a stable identity EngineeringElement TerminalFn
(=>
(instance ?COMP EngineeringComponent)
(exists (?DEVICE)
(and
(instance ?DEVICE Device)
(component ?COMP ?DEVICE))))

EngineeringConnection An EngineeringConnection is an EngineeringComponent that represents a connection relationship between two other EngineeringComponents. It is a reification of the Predicate connectedEngineeringComponents. That means that whenever this Predicate holds between two EngineeringComponents, there exists an EngineeringConnection. The practical reason for reifying a relationship is to be able to attach other information about it. For example, one might want to say that a particular connection is associated with some shared parameters, or that it is of a particular type. EngineeringConnections are EngineeringComponents and can therefore be an engineeringSubcomponent of other EngineeringComponents. However, to provide for modular regularity in component systems, EngineeringConnections cannot be connected. For each pair of EngineeringComponents related by connectedEngineeringComponents, there exists at least one EngineeringConnection. However, that object may not be unique, and the same EngineeringConnection may be associated with several pairs of EngineeringComponents EngineeringComponent connectsEngineeringComponents
(=>
(instance ?CONNECTION EngineeringConnection)
(exists (?COMP1 ?COMP2)
(connectsEngineeringComponents ?CONNECTION ?COMP1 ?COMP2)))

Subject	documentation	is a kind of	be first domain of	have axiom
EngineeringComponent	A fundamental concept that applies in many engineering domains. An EngineeringComponent is an EngineeringElement that is a physically whole object, such as one might see listed as standard parts in a catalog. The main difference betweeen EngineeringComponents and arbitrary globs of matter is that EngineeringComponents are object-like in a modeling sense. Thus, an EngineeringComponent is not an arbtrary subregion, but a part of a system with a stable identity	EngineeringElement	TerminalFn	(=> (instance ?COMP EngineeringComponent) (exists (?DEVICE) (and (instance ?DEVICE Device) (component ?COMP ?DEVICE))))
EngineeringConnection	An EngineeringConnection is an EngineeringComponent that represents a connection relationship between two other EngineeringComponents. It is a reification of the Predicate connectedEngineeringComponents. That means that whenever this Predicate holds between two EngineeringComponents, there exists an EngineeringConnection. The practical reason for reifying a relationship is to be able to attach other information about it. For example, one might want to say that a particular connection is associated with some shared parameters, or that it is of a particular type. EngineeringConnections are EngineeringComponents and can therefore be an engineeringSubcomponent of other EngineeringComponents. However, to provide for modular regularity in component systems, EngineeringConnections cannot be connected. For each pair of EngineeringComponents related by connectedEngineeringComponents, there exists at least one EngineeringConnection. However, that object may not be unique, and the same EngineeringConnection may be associated with several pairs of EngineeringComponents	EngineeringComponent	connectsEngineeringComponents	(=> (instance ?CONNECTION EngineeringConnection) (exists (?COMP1 ?COMP2) (connectsEngineeringComponents ?CONNECTION ?COMP1 ?COMP2)))

Up: EngineeringComponent