Skip to content

Commit

Permalink
Apply suggestions from code review
Browse files Browse the repository at this point in the history
Co-authored-by: Jason Desrosiers <[email protected]>
  • Loading branch information
gregsdennis and jdesrosiers authored Oct 21, 2024
1 parent 3f547ac commit de4ba41
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions jsonschema-core.md
Original file line number Diff line number Diff line change
Expand Up @@ -907,8 +907,8 @@ to establish a base IRI in order to resolve the reference.
#### The `$id` Keyword {#id-keyword}

The `$id` keyword identifies a schema resource. The value for this keyword MUST
be a string, and MUST represent a valid [IRI reference](#rfc3987) (without a
fragment).
be a string, and MUST represent a valid [IRI reference](#rfc3987) without a
fragment.

When the value of this keyword is resolved against the current base IRI, the
resulting absolute IRI then serves as the identifier for the schema resource and
Expand Down Expand Up @@ -1262,7 +1262,7 @@ desired to identify the object containing the `$ref` in the second

Due to the potential break in functionality described above, the behavior for
using JSON Pointer fragments that point to or cross a resource boundary is
undefined. Schema authors SHOULD NOT rely on such IRIs, as using them may
undefined. Schema authors SHOULD NOT rely on such IRIs, as using them may
reduce interoperability.[^8]

[^8]: This is to avoid requiring implementations to keep track of a whole stack
Expand Down

0 comments on commit de4ba41

Please sign in to comment.