-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is xs:sequence intended? #175
Comments
According to my XMLSpy validation this is the only valid way to construct the XSD. I think it has to do with the reuse of parts of the schema. |
Sounds like it should be
|
I can only second @andyward. I was very confused when I came across this while giving a TS implementation a try. If the order isn't adding any value please us |
ok; looking for feedback from others as well |
Sounds like a good suggestion if random order is intended. I do like seeing the nodes in the same order in files though. Also makes it easy to query by index. |
There's no semantic need for constraining the order.
I second the schema change that Andy suggests. It is more tolerant, but
retains backwards compatibility.
…On Thu, Sep 21, 2023, 17:26 SergejMuhic ***@***.***> wrote:
Sounds like a good suggestion if random order is intended.
I do like seeing the nodes in the same order in files though. Also makes
it easy to query by index.
—
Reply to this email directly, view it on GitHub
<#175 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABJY7MLBLEF3HVVTEZN3Z5TX3RMDPANCNFSM6AAAAAA2SOTYBM>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
@SergejMuhic FYI querying by index might be dangerous, as a lot of the items in the sequences are optional (marked with |
Missed that. I will not query by index! 😄 |
|
In the call we have identified some value of keeping sequences in order:
So the decision is to keep the sequence elements. |
Because xs:sequence is used, that means that the description element must be exactly in that position and in no other. Is this intentional? Sounds like it's just a pain with no real meaning.
I've noticed others and most recently IfcOpenShell/IfcOpenShell#3476 who seem to write IDSes by hand run into this problem.
The text was updated successfully, but these errors were encountered: