Update XSD for version 1.6 #77
Merged
Conversation
This file contains hidden or 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
I forgot to do this when I bumped the document version a few commits ago. The main effect is to allow the value "1.6" for the version attribute of the VOTABLE element. That may be the only substantial difference between the 1.5 and 1.6 schemas, but possibly we'll come up with some other things before 1.6 REC. I'm following previous VOTable practice by labelling the xs:schema element with the attribute version="1.6pre" while 1.6 is still under development. I'm not exactly sure what the effect of that is, but I think it's at least harmless (as long as we remember to change it to "1.6" before REC).
msdemlei
approved these changes
Feb 4, 2026
Collaborator
msdemlei
left a comment
msdemlei
left a comment
There was a problem hiding this comment.
I tend to call pre-release versions of schema files -wd1, -wd2, -pr1... so it's simpler to figure out a schema file's origin when you bump into one years later in some long-forgotten repo; but then a simple -pre (and then -pre1, -pre2...) is good enough, I guess.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I forgot to do this when I bumped the document version a few commits ago. The main effect is to allow the value "1.6" for the version attribute of the VOTABLE element.
That may be the only substantial difference between the 1.5 and 1.6 schemas, but possibly we'll come up with some other things before 1.6 REC.
I'm following previous VOTable practice by labelling the xs:schema element with the attribute version="1.6pre" while 1.6 is still under development. I'm not exactly sure what the effect of that is, but I think it's at least harmless (as long as we remember to change it to "1.6" before REC).