Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit d152894

Browse files
jdesrosiersgregsdennis
andcommitted
Incorporate feedback from Greg
Co-authored-by: Greg Dennis <gregsdennis@yahoo.com>
1 parent 6274757 commit d152894

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

‎specs/jsonschema-core.md‎

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -963,7 +963,7 @@ fragments as an alternative to JSON Pointers.[^4] See {{fragments}}.
963963

964964
[^4]: Note that the anchor string does not include the "#" character, as it is
965965
just a fragment identifier not an IRI reference. To reference the "foo"
966-
`$anchor` from the same Schema Resource, you would use the fragment-only IRI
966+
`$anchor` from the same schema resource, you would use the fragment-only IRI
967967
`#foo`. See below for full examples.
968968

969969
`$dynamicAnchor` defines a different kind of identifier that only has meaning
@@ -993,8 +993,7 @@ applicators, applying the referenced schema to the instance.
993993
##### Direct References with `$ref` {#ref}
994994

995995
The `$ref` keyword is an applicator that is used to reference a statically
996-
identified schema. Its results are the results of evaluating the referenced
997-
schema.[^5]
996+
identified schema. Its results are the results of the referenced schema.[^5]
998997

999998
[^5]: Note that this definition of how the results are determined means that
1000999
other keywords can appear alongside of `$ref` in the same schema object.
@@ -1206,10 +1205,11 @@ each resource is a separate document connected with [schema
12061205
references](#referenced), or is structured as a single document with one or more
12071206
schema resources embedded as subschemas.
12081207

1209-
Since IRIs with JSON Pointer fragments relative to the parent schema
1210-
resource's IRI cease to be valid when the embedded schema is moved to a separate
1211-
document and referenced, applications and schemas SHOULD NOT use such IRIs to
1212-
identify embedded schema resources or locations within them.
1208+
Since IRIs with JSON Pointer fragments are relative to the parent schema
1209+
resource's IRI, they cease to be valid when the embedded schema is moved to a
1210+
separate document and referenced. Because of this, applications and schemas
1211+
SHOULD NOT use such IRIs to identify embedded schema resources or locations
1212+
within them.
12131213

12141214
Consider the following schema document that contains another schema resource
12151215
embedded within it:

0 commit comments

Comments
(0)

AltStyle によって変換されたページ (->オリジナル) /