Skip to content
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

Fix <item-name> in schemas. #754

Closed
spoeschel opened this issue May 16, 2018 · 2 comments
Closed

Fix <item-name> in schemas. #754

spoeschel opened this issue May 16, 2018 · 2 comments

Comments

@spoeschel
Copy link

<item-name> allows either one of two specific tokens or a QName as value. The XSD however does not reflect this at the moment.

@skynavga skynavga added this to the CR2 milestone May 16, 2018
@skynavga skynavga changed the title Fix <item-name> in XSD schema Fix <item-name> in schemas. May 16, 2018
skynavga added a commit that referenced this issue May 16, 2018
@skynavga skynavga self-assigned this May 16, 2018
@spoeschel
Copy link
Author

Regarding the QName, both schemas currently instead require xs:anyURI though (e.g. a:b:c is allowed but shouldn't). I'm not sure if this was intended to be fixed in a separate MR...

skynavga added a commit that referenced this issue May 17, 2018
@skynavga
Copy link
Collaborator

@spoeschel good catch

skynavga added a commit that referenced this issue May 20, 2018
@skynavga skynavga removed their assignment May 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants