Commit 8407415

gregsdennisjdesrosiers

and

committed

Apply suggestions from code review

Co-authored-by: Jason Desrosiers <jdesrosi@gmail.com>

1 parent 636aa37 commit 8407415Copy full SHA for 8407415

File tree

-3

lines changed

-3

lines changed

Lines changed: 3 additions & 3 deletions

Original file line number	Diff line number	Diff line change
`@@ -907,8 +907,8 @@ to establish a base IRI in order to resolve the reference.`
`907`	`907`	#### The `$id` Keyword {#id-keyword}
`908`	`908`
`909`	`909`	The `$id` keyword identifies a schema resource. The value for this keyword MUST
`910`		`-be a string, and MUST represent a valid [IRI reference](#rfc3987) (without a`
`911`		`-fragment).`
	`910`	`+be a string, and MUST represent a valid [IRI reference](#rfc3987) without a`
	`911`	`+fragment.`
`912`	`912`
`913`	`913`	`When the value of this keyword is resolved against the current base IRI, the`
`914`	`914`	`resulting absolute IRI then serves as the identifier for the schema resource and`
@@ -1262,7 +1262,7 @@ desired to identify the object containing the `$ref` in the second
`1262`	`1262`
`1263`	`1263`	`Due to the potential break in functionality described above, the behavior for`
`1264`	`1264`	`using JSON Pointer fragments that point to or cross a resource boundary is`
`1265`		`-undefined. Schema authors SHOULD NOT rely on such IRIs, as using them may`
	`1265`	`+undefined. Schema authors SHOULD NOT rely on such IRIs, as using them may`
`1266`	`1266`	`reduce interoperability.[^8]`
`1267`	`1267`
`1268`	`1268`	`[^8]: This is to avoid requiring implementations to keep track of a whole stack`

Comments

(0)