-
Notifications
You must be signed in to change notification settings - Fork 46
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
release-schema: update tag and publisher description for compiled releases #1712
base: 1.2-dev
Are you sure you want to change the base?
Conversation
schema/release-schema.json
Outdated
@@ -27,13 +27,13 @@ | |||
}, | |||
"publisher": { | |||
"title": "Publisher", | |||
"description": "The original publisher of this release.", | |||
"description": "The original publisher of the release. For a compiled release this may differ from the publisher(s) of the individual releases about the contracting process.", |
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.
Use non-normative synonym. Add "or planning process".
"description": "The original publisher of the release. For a compiled release this may differ from the publisher(s) of the individual releases about the contracting process.", | |
"description": "The original publisher of the release. The publisher of a compiled release for a contracting or planning process might differ from the publishers of its releases.", |
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.
But the schema is supposed to be normative?
Agree with the rest of the re-wording and have applied
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 think the first sentence sets the normative semantics, and the second sentence provides some additional guidance to aid interpretation. I might be wrong, though!
Co-authored-by: Duncan Dewhurst <[email protected]>
closes #330