-
-
Notifications
You must be signed in to change notification settings - Fork 266
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
Move "readOnly" from Hyper-Schema to Validation #378
Commits on Sep 8, 2017
-
Move "readOnly" from Hyper-Schema to Validation
We move the description and schema definition of "readOnly" verbatim from the Hyper-Schema specification (and meta-schema) to the validation one, in the "Metadata keywords" section (along with "default", in particular). This addresses part of json-schema-org#363, which states that some keywords historically in the Hyper-Schema specification would be better in the Validation document. The main argument for moving keywords such as "readOnly" is that the Hyper-Schema document could then only focus on describing the hypermedia linking model.
Configuration menu - View commit details
-
Copy full SHA for 6787975 - Browse repository at this point
Copy the full SHA 6787975View commit details -
Fix the "default" value of "readOnly" in its schema definition
Change from the "false" string to the `false` Boolean value.
Configuration menu - View commit details
-
Copy full SHA for 9f2b798 - Browse repository at this point
Copy the full SHA 9f2b798View commit details -
Configuration menu - View commit details
-
Copy full SHA for 203cc1c - Browse repository at this point
Copy the full SHA 203cc1cView commit details -
Configuration menu - View commit details
-
Copy full SHA for 605af84 - Browse repository at this point
Copy the full SHA 605af84View commit details -
Move type description of readOnly in its own paragraph
As is done for all other keywords.
Configuration menu - View commit details
-
Copy full SHA for 3af480b - Browse repository at this point
Copy the full SHA 3af480bView commit details -
Remove readOnly's description in validation meta-schema
The readOnly is property is actually the only one having a description; it got inherited when moved from hyper-schema meta-schema. So drop it to be consistent with the rest of the schema. Additionnally, the current description contains ambiguous "server language" which we try to avoid.
Configuration menu - View commit details
-
Copy full SHA for c8874a7 - Browse repository at this point
Copy the full SHA c8874a7View commit details -
Replace "user agent" by "application" in readOnly description
The term "user agent" is appropriate in the scope of hypermedia, not that much elsewhere; "application" is more generic.
Configuration menu - View commit details
-
Copy full SHA for b4dc551 - Browse repository at this point
Copy the full SHA b4dc551View commit details -
Configuration menu - View commit details
-
Copy full SHA for 1d18f8f - Browse repository at this point
Copy the full SHA 1d18f8fView commit details -
Mention that readOnly can be used for UI generation
Echoing the document abstract.
Configuration menu - View commit details
-
Copy full SHA for 369648b - Browse repository at this point
Copy the full SHA 369648bView commit details