ArturTomczak
I don't hear anyone against it, so let's add this one to the docs and test cases.
If that's about the explanation of what it means in the standard, we do have it in the docs and let's keep the schema lean: https://github.com/buildingSMART/IDS/blob/development/Documentation/specifications.md https://github.com/buildingSMART/IDS/blob/development/Documentation/attribute-facet.md etc.
The `xs:all` (and `xs:any`) is not suited, I think, because it only allows for one element of a kind (the `maxOccurs` can be only 0 or 1 and we need...
To solve this, we could we leave xs:sequence (because: https://github.com/buildingSMART/IDS/issues/175#issuecomment-1744634900), but remove: from https://github.com/buildingSMART/IDS/blob/eff6e5763c579011ca2f70dd574b7f1d6a144816/Schema/ids.xsd#L113C15-L113C37 to prevent multiple entity facets.
How about using: `` instead of all sequences (see: https://stackoverflow.com/questions/28523597/meaning-of-minoccurs-and-maxoccurs-for-xsdchoice). This would also resolve #205.
you're right, let's update the table after repo housekeeping is finished #335
Apologies, my bad. Fixed them in the commits ~~above~~below.
I agree with your point that it is currently unprecise. I also agree that, in most cases, volume is more important. However, I'm not so sure everyone would agree with...
The tolerance.md file is now added to the development (#317).
please confirm if this can be closed now @rubendel @CBenghi