-
-
Notifications
You must be signed in to change notification settings - Fork 315
Improve the hyper-schema abstract #461
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
Conversation
jsonschema-hyperschema.xml
Outdated
vocabularies. This document specifies a vocabulary | ||
for annotating JSON documents with hyperlinks and instructions for processing and | ||
manipulating remote JSON resources through hypermedia environments such as HTTP. | ||
JSON Schema is a JSON based-format for describing JSON data using various |
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.
Do you mean "JSON-based format"?
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.
Heh. Yup, thanks, will fix.
Given the two approvals and the only comment from the third person being a trivial typo, I'm going to go ahead and merge now the the typo is fixed. |
Use language more in line with recent changes and recently introduced concepts. Add a little more detail about the general capabilities. This is all roughly inspired by reading the guidelineson abstracts in RFC 7322 section 4.3
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.
Next we might want to look at reworking the first sentence, coming back to this it's not immediately apparent what is meant by "vocabularies" (even though I wrote it).
@awwright good point on "vocabularies". |
Use language more in line with recent changes and recently
introduced concepts. Add a little more detail about the
general capabilities. This is all roughly inspired by reading
the guidelineson abstracts in RFC 7322 section 4.3