Clarify the use of plain name fragments. #356
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Also clarify that internal referencing allows skipping the process of resolving URI references. Addresses issue json-schema-org#318.
Closed
This addresses the trivial portion of issue json-schema-org#349.
|
Thanks, @handrews. The sentence about relocatable schemas is great: it both clarifies the use of fragments and, more importantly, highlights useful functionality for schema design. Thanks for pushing this through. |
|
Since this is just a clarification and it's been open for more than a week, a project member approved the idea in the original issue, and the original filer has approved this wording, I'm going to go ahead and merge. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Also clarify that internal referencing allows skipping the process
of resolving URI references.
Addresses issue #318.
@reece, I ended up changing your suggestion a bit and putting some up in the "how to define an
$id" section and some in the section you noted about how internal reference resolution works. Please let me know if that still makes sense.