1851 Make ?variety optional; explain namespace-sensitive #1878
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
michaelhkay
added
XQFO
ChristianGruen
approved these changes
Mar 14, 2025
ChristianGruen
added
the
Propose Merge without Discussion
michaelhkay
added
Tests Added
|
The CG agreed to merge this PR without discussion at meeting 114 |
michaelhkay
added
Completed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix #1851
Allow ?variety to be absent e.g. for xs:anySimpleType
Define namespace-sensitive by an xtermref to the definition in the XP/XQ spec.