An IfcProjectLibrary collects all library elements that are included within a referenced project data set.
Examples for project libraries include:
The inherited attributes RepresentationContext and UnitsInContext have the following meaning:
NOTE It is generally discouraged to use a different length measure and plane angle measure in an included project library compared with the project itself. It may lead to unexpected results for the shape representation of items included in the project library.
Instances of IfcProjectLibrary are assigned to the project context using the IfcRelDeclares relationship and accessible through the inverse attribute HasContext. Individual object types and property (set) templates are assigned to the IfcProjectLibrary using the IfcRelDeclares relationship and are accessible through the inverse attribute Declares. An IfcProjectLibrary may be decomposed into sub libraries using the relationship IfcRelNests. Sub libraries are accessed by the IfcProjectLibrary through the inverse attribute IsNestedBy.
HISTORY New entity in IFC4.
|1||GlobalId||IfcGloballyUniqueId||[1:1]||Assignment of a globally unique identifier within the entire software world.||X|
Assignment of the information about the current ownership of that object, including owning actor, application, local identification and information captured about the recent changes of the object,
NOTE only the last modification in stored - either as addition, deletion or modification.
|3||Name||IfcLabel||[0:1]||Optional name for use by the participating software systems or users. For some subtypes of IfcRoot the insertion of the Name attribute may be required. This would be enforced by a where rule.||X|
|4||Description||IfcText||[0:1]||Optional description, provided for exchanging informative comments.||X|
|S[0:?]||Reference to the relationship objects, that assign (by an association relationship) other subtypes of IfcObject to this object instance. Examples are the association to products, processes, controls, resources or groups.||X|
|S[0:1]||References to the decomposition relationship being a nesting. It determines that this object definition is a part within an ordered whole/part decomposition relationship. An object occurrence or type can only be part of a single decomposition (to allow hierarchical strutures only).|
|S[0:?]||References to the decomposition relationship being a nesting. It determines that this object definition is the whole within an ordered whole/part decomposition relationship. An object or object type can be nested by several other objects (occurrences or types).||X|
|S[0:1]||References to the context providing context information such as project unit or representation context. It should only be asserted for the uppermost non-spatial object.|
|S[0:?]||References to the decomposition relationship being an aggregation. It determines that this object definition is whole within an unordered whole/part decomposition relationship. An object definitions can be aggregated by several other objects (occurrences or parts).||X|
|S[0:1]||References to the decomposition relationship being an aggregation. It determines that this object definition is a part within an unordered whole/part decomposition relationship. An object definitions can only be part of a single decomposition (to allow hierarchical strutures only).||X|
|S[0:?]||Reference to the relationship objects, that associates external references or other resource definitions to the object.. Examples are the association to library, documentation or classification.||X|
The object type denotes a particular type that indicates the object further. The use has to be established at the level of instantiable subtypes.
NOTE Subtypes of IfcContext do not introduce a PredefinedType attribute, therefore the usage of ObjectType is not bound to the selection of USERDEFINED within the PredefinedType enumaration.
|6||LongName||IfcLabel||[0:1]||Long name for the context as used for reference purposes.||X|
|7||Phase||IfcLabel||[0:1]||Current project phase, or life-cycle phase of this project. Applicable values have to be agreed upon by view definitions or implementer agreements.||X|
|8||RepresentationContexts||IfcRepresentationContext||S[1:?]||Context of the representations used within the context. When the context is a project and it includes shape representations for its components, one or several geometric representation contexts need to be included that define e.g. the world coordinate system, the coordinate space dimensions, and/or the precision factor.||X|
|9||UnitsInContext||IfcUnitAssignment||[0:1]||Units globally assigned to measure types used within the context.||X|
|S[0:?]||Set of relationships to property set definitions attached to this context. Those statically or dynamically defined properties contain alphanumeric information content that further defines the context.|
|S[0:?]||Reference to the IfcRelDeclares relationship that assigns the uppermost entities of includes hierarchies to this context instance.
NOTE The spatial hiearchy is assigned to IfcProject using the IfcRelAggregates relationship. This is a single exception due to compatibility reasons with earlier releases.
Libraries of components standardized by DOT agencies may be referenced from external locations and encapsulated within project libraries. Such components may include DOT-standardized assemblies for piers, abutments, and bridge decks, as well as more general-purpose shapes such as AISC steel shapes and ACI rebar bending types.
As units may vary between components, each library may define its own.
The Project Declaration concept applies to this entity.
The Project Units concept applies to this entity.
Link to this page