search

buildingSMART / IDS

Computer interpretable (XML) standard to define Information Delivery Specifications for BIM (mainly used for IFC)
Other
167 stars 52 forks source link

Extended Relationship Facet #248

Closed NickNisbet closed 2 months ago

NickNisbet commented 2 months ago

I would like to specify B. That every significant element should have type.

Both as an applicability (anything with a Type should have a quantity) and as a requirement (anything bigger than 0.1m3 should have a type object.

MatthiasWeise commented 2 months ago

New feature for IDS 2.0? However, I wonder if such kind of checks should be covered by IDS at all. By design IDS wants to hide schema details from the user to be easy to use. Main focus is on availability/correctness of content, but not how it is encoded in IFC (property attached to occurrence or type object does not matter).

pjanck commented 2 months ago

I wonder if such kind of checks should be covered by IDS at all

Agreed. This is outside of scope of IDS in my perception as well (even for 2.0).

every significant element should have type

@NickNisbet I propose to use mvdXML to require this.

CBenghi commented 2 months ago

Indeed, here we want to make sure that the information is provided. As long as it's provided according to the IFC best practice, we should be satisfied. Let IFC deal with file quality, we are all about information!