You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The IDS documentation states that only enumerated attributes in the documentation might be specified (because the others are inverse ones). However, the enumerated ones have again two types: ones with explicit values like Name or Description and ones with references to other entities, like for the RelatingSpace attribute. It seems IDS only allows attributes with explicit values. The example above does comply with the IDS schema, but the IDS audit tool, for example, does not allow it.
Is the attribute facet intended to be used for this case?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I tried to use the attribute facet to define which entity should be referenced by an attribute. For example, defining that the RelatingSpace attribute of IfcRelSpaceBoundary2ndLevel must be an IfcSpace (https://ifc43-docs.standards.buildingsmart.org/IFC/RELEASE/IFC4x3/HTML/lexical/IfcRelSpaceBoundary2ndLevel.htm):
The IDS documentation states that only enumerated attributes in the documentation might be specified (because the others are inverse ones). However, the enumerated ones have again two types: ones with explicit values like Name or Description and ones with references to other entities, like for the RelatingSpace attribute. It seems IDS only allows attributes with explicit values. The example above does comply with the IDS schema, but the IDS audit tool, for example, does not allow it.
Is the attribute facet intended to be used for this case?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions