4.1.3.1.4 System Element Attributes
NOTE: This template for attributes, like similar ones, originates from legacy requirements tied to mvdXML and an earlier era when MVD defined exchange information requirements. Such templates no longer add value to the specification, nor do they convey information beyond what is already defined in the schema. Additionally, some templates reference deprecated entities, potentially causing unnecessary confusion.
As part of a broader effort to clean up documentation, this and other non-essential templates will be removed in the next release.
The following diagram shows the generic classes and relationships used when applying this concept.
In addition, concepts may have particular importance to common or standardised industry practices and scenarios. For these specific usage scenarios, the table below shows a recommended list of general usage patterns that users may adopt.
%3
IfcSystem
IfcSystem
1. GlobalId
[1:1]
2. OwnerHistory
[0:1]
Name
3. Name
[0:1]
4. Description
[0:1]
Decomposes
[0:1]
HasAssignments
[0:?]
HasAssociations
[0:?]
HasContext
[0:1]
IsDecomposedBy
[0:?]
IsNestedBy
[0:?]
Nests
[0:1]
5. ObjectType
[0:1]
Declares
[0:?]
IsDeclaredBy
[0:1]
IsDefinedBy
[0:?]
IsTypedBy
[0:1]
IsGroupedBy
[0:?]
ReferencedInStructures
[0:?]
ServicesBuildings
[0:1]
ServicesFacilities
[0:?]
IfcLabel
IfcLabel
IfcSystem:Name1->IfcLabel:IfcLabel0
Figure 4.1.3.1.4.A
Table A
