-
-
Notifications
You must be signed in to change notification settings - Fork 330
add subsection to point to the github process file for proposal requirements #1613
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
base: main
Are you sure you want to change the base?
Conversation
specs/jsonschema-core.md
Outdated
@@ -437,6 +437,13 @@ compatible with successive specifications, which are published with the same | |||
version and either the same or greater release year value. Thus, JSON Schema | |||
provides a guarantee of compatibility for future releases within a version. | |||
|
|||
### Future Development and Support of Proposals | |||
|
|||
Continued development of this specifications and support requirments for |
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.
Continued development of this specifications and support requirments for | |
Continued development of this specification and support requirements for |
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.
Oh, yeah, I meant for that to go the other way. Should be "these specifications" to include the validation spec.
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.
With the already suggested change 👍🏻
What kind of change does this PR introduce?
clarification
Issue & Discussion References
Summary
Adds a new section to help identify requirements for proposals.
It does feel odd to me that the specification is now pointing to a document that could be (and still needs to be) updated.
Does this PR introduce a breaking change?
No.