MarcelStepien

I would recommend doing so. The identifier can be UUID based string and should be used to differentiate specifiactions. In my opinion, it should be required, if multiple specifications are...

@CBenghi you mentioned that the files should be stored in a different folder rather then root. Can you name a folder path I should use?

@CBenghi I will be able to provide an overview of the state of test-cases once we converted all to the newer version of IDS.

Just to add my option on the matter of the cardinality in regard to to **required** and **prohibited**, I agree that an IDS specific solution would solve a lot of...

@berlotti I discussed and presented this concept in the IDS development meetings. This was meant to be a first working proposal for migration using XSLT. The intention was to transfer...

The current solution is, that IFCRELVOIDSELEMENT and IFCRELFILLSELEMENT relations had been combined into one single option "IFCRELVOIDSELEMENT_IFCRELFILLSELEMENT". This option performs a two steps iteration through the relations and checks for...

@berlotti yes, my bad. Depending on how you generate the class structure from the xsd, it automatically adds a '_' inbetween (since its translated to an enumeration). The option is...

There is also the connection to **IfcMaterialUsageDefinition** via the **IfcMaterialSelect** class hierarchy. In our tests with the material facet we discovered that some prominent software vendors prefer the material export...

Update of the review in retrospect to the latest IDS version. 1) fail - a prohibited facet returns the opposite of a required facet This should work now, since the...

In my opinion the base-restriction is obsolete, since it is indirectly inferred by the datatype/measure in a property-facet (**IFCTEXT** checks for **xs:string**, **IFCREAL** checks for **xs:double**). In all other facets,...