MatthiasWeise

> Note that we have agreed not to allow this [#29 (comment)](https://github.com/buildingSMART/IDS/issues/29#issuecomment-1040245815) Good point, keep it simple! Then we need to split into two specifications (first option).

Changing the namespace from xs to ids sounds a good compromise if we want to keep cardinality for future IDS versions (although I agree that renaming shouldn't be a deal...

Yes, this topic is open for discussion. Please add you opinion to this issue! This question already came up for mvdXML 1.1, but we then decided to keep the string-based...

My interpretation is that `measure ` is mandatory according to the IDS schema and has to stick to IFC Defined types (see link in documenation including `IfcLabel, IfcText, IfcBoolean, IfcMonetaryMeasure`...

Agree with Nick, there is no reason to differentiate between Applicability and Requirement.

> * I think must contain boundary relations between connection points (slave points), if this could be possible to be described with ifc entities. I am not fully sure what...

So you need to define a mechanical connection between two nodes that are at the same location? My understanding for defining DOF between members and surrounding: The model differentiates between...

Is this a slab to be represented by a structural surface member and N9 is a node within this surface member? What is the meaning of N9, is it a...

Might be an extension to current definition then. If it can be handled by addtional information in IfcBoundaryNodeCondition it might be a new subtype in future IFC releases (similar to...

> If it's a one to one relationship, in my developments I have supported a user defined object type on a curve member and custom properties to nominate DOF. I'm...