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
Text changes for issue #388 #535
Conversation
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.
I wonder whether we want to call them map attributes only informally. Shouldn’t we make a proper termdef with firstterm of it?
If the text stays as it is, at least use typographic quotes (“map attribute” instead of "map attribute").
I now made "map-attribute" an official termdef. Better? |
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.
Approve, but consider changing “datatype” to “sequence type”
Changed the wordings to make it adhere to the definition of AVT
Ok, datatype is now sequence type. |
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.
♫♪
Ah you can merge if you want to, you can leave your peers behind
Cause your peers don't merge and if they don't merge
Well they're are no peers of mine
…
— Men At Work
Men Without Hats, apparently… |
Aren't we all (in the committee). I haven't seen a hat on our heads in Leipzig :-) |
I tried to describe map attributes and moved the section about option attributes to the right location