Required elements: | None |
Optional elements: | None |
Required attributes: | XMLID , DayComponent , MonthComponent , YearComponent |
Optional attributes: | None |
Definition from ISO/CD 10303-41:1992: A date which is defined by a day in a monthof a year.
HISTORY This entity has changes after IFC Release 1.5.1.
Attribute: | XMLID |
---|---|
Description: |
|
Type: | id |
Attribute: | DayComponent | ||||
---|---|---|---|---|---|
Description: |
|
||||
Type: | int |
Attribute: | MonthComponent | ||||
---|---|---|---|---|---|
Description: |
|
||||
Type: | int |
Attribute: | YearComponent | ||||
---|---|---|---|---|---|
Description: |
|
||||
Type: | int |
Required elements: | None |
Optional elements: | None |
Required attributes: | XMLID , Source , Edition , Name |
Optional attributes: | EditionDate , Contains |
Definition from IAI: An IfcClassification is used for the arrangement of objects into a class or category according to a common purpose or their possession of common characteristics.
HISTORY: New class in IFC Release 1.5. It has changed in IFC Release 2x.
ISSUES: See issue and change log for changes made in IFC Release 2x.
In previous releases of IFC, the IfcClassification class was used as the means for connecting classifications to objects. This is no longer the case for IFC Release 2x, the IfcClassificationNotation Class having taken on this role. IfcClassification is now used to identfy the classification system or source from which a classification notation is derived. The objective is to minimize the number of IfcClassification objects contained within an IFC model. Ideally, each classification system or source used should have only one IfcClassification object. However, because multiple classification is allowed, there may be many IfcClassification objects used, each identifying a different classification system or source. An example of the use of the IfcClassification class is:
#1 IFCCALENDARDATE (31,8,1997);#2 IFCCLASSIFICATION(RIBA,1,#1,Uniclass)
Attribute: | XMLID |
---|---|
Description: |
|
Type: | id |
Attribute: | Source | ||||
---|---|---|---|---|---|
Description: |
|
||||
Type: | string |
Attribute: | Edition | ||||
---|---|---|---|---|---|
Description: |
|
||||
Type: | string |
Attribute: | Name | ||||
---|---|---|---|---|---|
Description: |
|
||||
Type: | string |
Attribute: | EditionDate | ||||
---|---|---|---|---|---|
Description: |
|
||||
Type: | idref - IfcCalendarDate |
Attribute: | Contains | ||
---|---|---|---|
Description: |
|
||
Type: | idrefs - IfcClassificationItem |
Required elements: | None |
Optional elements: | None |
Required attributes: | XMLID , Notation , Title |
Optional attributes: | ItemOf |
Definition from IAI: An IfcClassificationItem is a class of classification notations used.
Note: The term 'classification item' is used in preference to the term 'table' for improved flexibility. For example, the classification item "L681" in Uniclass may be used to contain all subsequent notation facets within that class of classifications which has the title "Proofings, insulation"(e.g. L6811, L6812, L6813 etc.).
HISTORY: New entity in IFC Release 2x.
ISSUES: See issue and change log for changes made in IFC Release 2x.
Usage of the IfcClassificationItem class is as follows:
#1 IFCCALENDARDATE (31,8,1997);
#2 IFCCLASSIFICATION(RIBA,1,#1,Uniclass)
#100 IFCCLASSIFICATIONOTATIONFACET ('L6814');
#200 IFCCLASSIFICATIONITEM (#100,#2,'Door Panel');
Attribute: | XMLID |
---|---|
Description: |
|
Type: | id |
Attribute: | Notation | ||||
---|---|---|---|---|---|
Description: |
|
||||
Type: | idref - IfcClassificationNotationFacet |
Attribute: | Title | ||||
---|---|---|---|---|---|
Description: |
|
||||
Type: | string |
Attribute: | ItemOf | ||||
---|---|---|---|---|---|
Description: |
|
||||
Type: | idref - IfcClassification |
Required elements: | None |
Optional elements: | None |
Required attributes: | XMLID , NotationFacets |
Optional attributes: | None |
Definition from IAI: An IfcClassificationNotation is a notation used from published reference (which may be either publicly available from a classification society or is published locally for the purposes of an organization, project or other purpose).
Note: A classification notation may be developed using various notation facets. A facet is a part of the actual notation but which has a specific meaning. For instance, it may be appropriate to classify an item by owning actor (represented by A=Architect) and by an entry from a classification table such as CI/SfB (represented by 210 for external wall). This gives a classification as A210
HISTORY: New class in IFC Release 1.5. It has changed in IFC Release 2x.
ISSUES: See issue and change log for changes made in IFC Release 2x.
All classifications of an object that are contained within the IFC model are made through the IfcClassificationNotation class (and not through IfcClassification as was the case up to R2.0). For a given object, the IfcRelAssociatesClassification class (contained within the IfcKernel) makes the connection between the IfcObject (abstract superclass, IfcDoor has been taken as an example for instantiation) and the IfcClassificationNotation. IfcObject <-- IfcRelAssociatesClassification --> IfcClassificationNotation. Consider an object that is to be classified with the notation "L6814". In this case, the IfcRelAssociatesClassification has the form:
#100 IFCDOOR (.....);
#200 IFCCLASSIFICATIONNOTATIONFACET ('L6814');
#300 IFCCLASSIFICATIONNOTATION ((#200));
#400 IFCRELASSOCIATESCLASSIFICATION ((#300),#100);
If the object is to have other notations (e.g. B2186 and Z6793), the IfcRelAssociatesClassification has the form:
#100 IFCDOOR (.....);
#200 IFCCLASSIFICATIONNOTATIONFACET ('L6814');
#210 IFCCLASSIFICATIONNOTATIONFACET ('B2186');
#220 IFCCLASSIFICATIONNOTATIONFACET ('Z6793');
#300 IFCCLASSIFICATIONNOTATION ((#200,#210,#220));
#400 IFCRELASSOCIATESCLASSIFICATION ((#300),#100);
It is a requirement that a classification notation can only bring together facets from the same classification system or source. Bringing together notation facets from different sources within the same classification notation is not allowed. However, since the IfcRelAssociatesClassification class does allow for multiple classifications to a single object, then it is possible to define multiple classification notations where each notation contains facets from a single source.
#100 IFCDOOR (.....);
#200 IFCCLASSIFICATIONNOTATIONFACET ('L6814');
#210 IFCCLASSIFICATIONNOTATIONFACET ('B2186');
#220 IFCCLASSIFICATIONNOTATIONFACET ('Z6793');
#300 IFCCLASSIFICATIONNOTATIONFACET ('106');
#400 IFCCLASSIFICATIONNOTATIONFACET ('A-31-623');
#410 IFCCLASSIFICATIONNOTATIONFACET ('B-62-562');
#500 IFCCLASSIFICATIONNOTATION ((#200,#210,#220));
#510 IFCCLASSIFICATIONNOTATION ((#300));
#520 IFCCLASSIFICATIONNOTATION ((#400,#410));
#600 IFCRELASSOCIATESCLASSIFICATION (#100,(#500,#510,#520));
Attribute: | XMLID |
---|---|
Description: |
|
Type: | id |
Attribute: | NotationFacets | ||||
---|---|---|---|---|---|
Description: |
|
||||
Type: | idrefs - IfcClassificationNotationFacet |
Required elements: | None |
Optional elements: | None |
Required attributes: | XMLID , NotationValue |
Optional attributes: | None |
Definition from IAI: An IfcClassificationNotationFacet is a group of alphanumeric characters used within a classification notation.
HISTORY: New class in IFC Release 1.5. This class has changed in IFC Release 2x and had been renamed from IfcNotationFacet.
ISSUE: See issue and change log for changes made in IFC Release 2x.
An IfcClassificationNotationFacet object holds an individual classification value that is to be assigned to an object through IfcClassificationNotation and IfcRelAssociatesClassification objects. For example:
Attribute: | XMLID |
---|---|
Description: |
|
Type: | id |
Attribute: | NotationValue | ||
---|---|---|---|
Description: |
|
||
Type: | string |
Required elements: | None |
Optional elements: | None |
Required attributes: | XMLID |
Optional attributes: | Location , ItemReference , Name , ReferencedSource |
Definition from IAI: An IfcClassificationReference is a reference into a classification system or source (see IfcClassification). An optional inherited ItemReferenced key is also provided to allow more specific references to classification items (or tables) by type. The inherited Name attribute allows for a human interpretable designation of a classification notation (or code) - see use definition of "Leightweight Classification".
HISTORY: New entity in IFC Release 2x.
ISSUES: See issue and change log for changes made in IFC Release 2x.
The IfcClassificationReference can be used as a form of 'lightweight' classification through the 'ItemReference' attribute inherited from the abstract IfcExternalReference class. In this case, the 'ItemReference' could take (for instance) the Uniclass notation "L6814" which, if the classification was well understood by all parties and was known to be taken from a particular classification source, would be sufficient. The Name attribute could be the title "Tanking". This would remove the need for the overhead of the more complete classification structure of the model.
However, it is not recommended that this lightweight method be used in cases where more than one classification system is in use or where there may be uncertainty as to the origin or meaning of the classifcation.
#100 IFCFLOWEQUIPMENT (.....);
#200 IFCCLASSIFICATIONREFERENCE ($,'L6814','Tanking',$);
#300 IFCRELASSOCIATESCLASSIFICATION ((#200),#100);
Classifications of an object may be referenced from an external source rather than being contained within the IFC model. This is done through the IfcClassificationReference class. Consider the Uniclass notation "L6814" which has the title "Tanking". In this case, the optional attribute 'ItemReference' uses the title 'Tanking' that would otherwise be applied to the IfcClassificationItem (if it was to be contained in the model). The location of the classification reference may be found from a classification server that is available via the Internet. In this case, it may be something like "http://www.ncl.ac.uk/classification/uniclass/tanking.htm#6814"
#1 IFCCALENDARDATE (31,8,1997);
#2 IFCCLASSIFICATION(RIBA,1,#1,Uniclass)
#100 IFCFLOWEQUIPMENT (.....);
#200 IFCCLASSIFICATIONREFERENCE ('http://www.ncl.ac.uk/classification/uniclass/tanking.htm#6814','L6814',$,#2);
#300 IFCRELASSOCIATESCLASSIFICATION ((#200),#100);
Because the relation between IfcRelAssociatesClassification and classification is actually made at the IfcClassificationNotationSelect class which allows classification to be either contained or referenced, it is possible to assign both contained and referenced classifications to an object.
#1 IFCCALENDARDATE (31,8,1997);
#2 IFCCLASSIFICATION(RIBA,1,#1,Uniclass)
#100 IFCFLOWEQUIPMENT (.....);
#200 IFCCLASSIFICATIONNOTATIONFACET ('L6814');
#210 IFCCLASSIFICATIONNOTATIONFACET ('B2186');
#220 IFCCLASSIFICATIONNOTATIONFACET ('Z6793');
#300 IFCCLASSIFICATIONNOTATION ((#200,#210,#220));
#400 IFCCLASSIFICATIONREFERENCE ('http://www.ncl.ac.uk/classification/uniclass/tanking.htm#6814','L6814',$,#2);
#500 IFCRELASSOCIATESCLASSIFICATION (#100,(#300,#400));
Attribute: | XMLID |
---|---|
Description: |
|
Type: | id |
Attribute: | Location | ||||||
---|---|---|---|---|---|---|---|
Description: |
|
||||||
Type: | string |
Attribute: | ItemReference | ||||||
---|---|---|---|---|---|---|---|
Description: |
|
||||||
Type: | string |
Attribute: | Name | ||||||
---|---|---|---|---|---|---|---|
Description: |
|
||||||
Type: | string |
Attribute: | ReferencedSource | ||||
---|---|---|---|---|---|
Description: |
|
||||
Type: | idref - IfcClassification |
Required elements: | None |
Optional elements: | IfcCalendarDate , IfcClassification , IfcClassificationItem , IfcClassificationNotation , IfcClassificationNotationFacet , IfcClassificationReference |
Required attributes: | None |
Optional attributes: | None |
Root document container & name for this schema