search

buildingSMART / bSDD

The buildingSMART Data Dictionary repository, where we publish the documentation, examples and more. We don't publish here the data, the source code of the bSDD service or the front end of the website.
https://www.buildingsmart.org/users/services/buildingsmart-data-dictionary/
MIT License
135 stars 36 forks source link

Use of Classes.RelatedIfcEntityNamesList in the case of a version-dependent IFC entity mapping? #95

Open MatthiasWeise opened 4 months ago

MatthiasWeise commented 4 months ago

For each class in my dictionary I am able to provide a list of related IFC entities. According to the documentation it seems that the IFC entity name is used for that, e.g. IfcWall as given in the example in the bSDD documentation.

What if the mapping depends on the IFC version, let's say it is IfcBuildingElementProxy in IFC2x3 and IFC4, and IfcBearing in IFC4.3? Can/shall I use a version qualifier in such cases (or maybe the URI)?

P.S. I know that bSDD does not yet include IFC versions other than IFC4.3, but I would expect some version dependency for future IFC versions as well.

atomczak commented 4 months ago

As you already noticed, we have only IFC4.3 as of now in the bSDD, hence, we are only referencing that one. My advice is to always use those classes that are shared among the versions, and if you must decide between them, it is better to go for the latest, 4.3.

In the situation that we will have more than one IFC version in bSDD, we are probably going to use the '.../latest/...' resolver, which looks for the latest version containing certain class.

Other options with versions or URIs are simply not supported.