status: mark schema v1.7 as Draft (under working-group review)#5
Merged
Conversation
Decouples maturity from the SemVer number (published V1.5/V1.6 tags + a forthcoming permanent Zenodo DOI mean the version cannot move backward to 0.x). Signals draft via a status label instead, kept consistent across surfaces and guarded by check_version.py. - schema.md header, README, llms.txt, schema-reference, .well-known/mcp-manifest.json, .zenodo.json: "Status: Draft -- under working-group review; the schema may change before ratification." - index.html + schema-reference JSON-LD: schema.org creativeWorkStatus = "Draft"; landing hero "v1.7 . Draft" and spec badge "draft". - check_version.py: new STATUS guard (8 markers / 7 files). Flip "Draft" -> "Stable" here (and the lines it points to) at committee ratification. check_version: 23 version labels + 8 status markers consistent. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Mark schema v1.7 as Draft (status, not a version change)
Per the decision that the version number can't move backward to 0.x (V1.5/V1.6 are tagged and a permanent Zenodo DOI is forthcoming), this signals draft maturity with a status label instead — decoupled from the SemVer number.
Open3DCP_SCHEMA.md,README.md,llms.txt,schema-reference,.well-known/mcp-manifest.json,.zenodo.json.creativeWorkStatus: "Draft"on the landing + schema-reference Dataset blocks; landing hero showsv1.7 · Draftand the spec badge readsdraft.scripts/check_version.pyextended with a STATUS check (8 markers / 7 files) so the label can't silently drift. At committee ratification, flip "Draft" → "Stable" there (and the lines it points to).No schema columns or version numbers change.
check_version.py: 23 version labels + 8 status markers consistent.🤖 Generated with Claude Code