7.11.3.2 IfcCaissonFoundationType

Assignment of a globally unique identifier within the entire software world.

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,

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.

Optional description, provided for exchanging informative comments.

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.

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).

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).

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.

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).

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).

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.

The attribute optionally defines the data type of the occurrence object, to which the assigned type object can relate. If not present, no instruction is given to which occurrence object the type object is applicable. The following conventions are used: * The IFC entity name of the applicable occurrence using the IFC naming convention, CamelCase with IFC prefix * It can be optionally followed by the predefined type after the separator "/" (forward slash), using uppercase * If one type object is applicable to many occurrence objects, then those occurrence object names should be separate by comma "," forming a comma separated string.

Set ~~list~~ of unique property sets, that are associated with the object type and are common to all object occurrences referring to this object type.

Reference to the relationship IfcRelDefinedByType and thus to those occurrence objects, which are defined by this type.

List of unique representation maps. Each representation map describes a block definition of the shape of the product style. By providing more than one representation map, a multi-view block definition can be given.

The tag (or label) identifier at the particular type of a product, e.g. the article number (like the EAN). It is the identifier at the specific level.

Reference to the IfcRelAssignsToProduct relationship, by which other products, processes, controls, resources or actors (as subtypes of IfcObjectDefinition) can be related to this product type.

The type denotes a particular type that indicates the object further. The use has to be established at the level of instantiable subtypes. In particular it holds the user defined type, if the enumeration of the attribute 'PredefinedType' is set to USERDEFINED.