-
Notifications
You must be signed in to change notification settings - Fork 11
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
Simplify element names of IDs #215
Conversation
I will have to change all examples. And it will create major problems with other PR, that don't do it. So. I will do it asap when a lot of things have already be merged. |
Is there a reason not to make this an attribute? |
Mostly history. I can change it to an attribute. |
They both would align things more to what it should be. However, (a) we don’t do it everywhere and we should move the id to an attribute in that case (b) in breaks a lot of implementations (c) It does not really simplify anything in a heavy way. I agree: It is hygiene, but I am not sure, if we should do it. |
Documentation updated. |
Also check references so |
fccad1c
49488b8
to
a6a67c8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes about the Id look correct and examples are also fixed. (Just made an optical check, did'n run them.)
0f6cda8
to
0e21b03
Compare
Question: As the type of those Ids were changed from xs:NMTOKEN to ObjectIdType - shouldn't we change the following as well? TripSummaryStructure.TripId |
Sounds reasonable, also from a validating perspective. |
Fixes #181 #179