Section 23 of 102
22. References and Relationships
Stable section ID: S05-CON-007-SECTION-23 · 41 content blocks
A Reference points to an Entity without copying its definition.
Reference syntax shall use a controlled form:
member: @Beam_B01;
profile: @US_NJ_Residential_Profile;
References may be:
local;
imported;
Registry-based;
external-resource references;
- version-pinned references.
- A Relationship shall be used where the association has engineering meaning.
Relationship types may include:
contains;
located_in;
connected_to;
supported_by;
supplies;
drains_to;
communicates_with;
controls;
monitors;
depends_on;
protects;
replaces;
certified_by.
Example:
relationship Beam_Node_Connection : structural_connection {
from: @Beam_B01.end_a;
to: @Node_N01.face_x_positive;
interface_profile: @S05_Structural_IF_03;
state: proposed;
}
Relationships may contain their own:
identity;
properties;
version;
state;
evidence;
- lifecycle history.
- Relationship direction shall be explicit where direction affects meaning.
Cardinality rules shall prevent invalid relationships, such as assigning one exclusive physical Interface to multiple simultaneous connections.