Clarify what is meant by JSON Pointer format.#354
Merged
handrews merged 1 commit intojson-schema-org:masterfrom Aug 30, 2017
Merged
Clarify what is meant by JSON Pointer format.#354handrews merged 1 commit intojson-schema-org:masterfrom
handrews merged 1 commit intojson-schema-org:masterfrom
Conversation
Addresses issue json-schema-org#328. URI fragment-encoded JSON Pointers are already handled by the "uri-reference" format, plus "pattern" if the media type supports multiple fragment types that would need to be disambiguated. Guidance on using "uri-reference" plus "pattern" belongs on the web site, so I did not add it to the spec.
dlax
approved these changes
Aug 21, 2017
Relequestual
approved these changes
Aug 30, 2017
gregsdennis
added
clarification
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Addresses issue #328. URI fragment-encoded JSON Pointers are
already handled by the "uri-reference" format, plus "pattern"
if the media type supports multiple fragment types that would
need to be disambiguated.
Guidance on using "uri-reference" plus "pattern" belongs on
the web site, so I did not add it to the spec.