Skip to content

Minor readability / clarity fixes #372

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

Merged
merged 5 commits into from
Aug 31, 2017
Merged

Conversation

handrews
Copy link
Contributor

Two very minor fixes that I'd included in the link context trial balloon. These aren't related to the bigger philosophical change in that PR.

@handrews handrews added this to the draft-07 (wright-*-02) milestone Aug 28, 2017
@handrews handrews requested review from dlax and Relequestual August 30, 2017 16:22
...before jumping into when you SHOULD NOT apply hyper-schema.

Reading over this for the first time in a few months, it was
a little abrupt.
For some reason I wrote this as an assertion rather than a
requirement in specification language.  Fixed.
In retrospect, this section ended up being rather confusing
since it assumed the reader understood the idea of an operation
as opposed to a link.  State that concept clearly.
"object as a whole" could be read to mean the entire schema
document, ignoring any intervening $id keywords.  This
clarifies that that is not the case.
Fix this wording to make it more clear that this requirement
is about fragment-only URI references, and that other sorts
of URI references are not constrained by this paragraph.
@handrews handrews mentioned this pull request Aug 30, 2017
@handrews handrews merged commit a560f8b into json-schema-org:master Aug 31, 2017
@handrews handrews deleted the clarity branch September 3, 2017 18:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants