Commit 713c353

committed

soften wording on absoluteKeywordLocation

it is not strictly true that there will *always* be a fragment in this field: an error might occur at the schema resource root itself (for example if the subschema is "false")

1 parent af9009b commit 713c353Copy full SHA for 713c353

File tree

1 file changed

-1

lines changed

jsonschema-core.xml

1 file changed

-1

lines changed

`‎jsonschema-core.xml`

Lines changed: 1 addition & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -2706,7 +2706,7 @@`
`2706`	`2706`	`Note that "absolute" here is in the sense of "absolute filesystem path"`
`2707`	`2707`	`(meaning the complete location) rather than the "absolute-URI"`
`2708`	`2708`	`terminology from RFC 3986 (meaning with scheme but without fragment).`
`2709`		`- Keyword absolute locations will always have a fragment in order to`
	`2709`	`+ Keyword absolute locations will have a fragment in order to`
`2710`	`2710`	`identify the keyword.`
`2711`	`2711`	`</cref>`
`2712`	`2712`	`</t>`

0 commit comments

Comments

(0)

Navigation Menu

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

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

Commit 713c353

File tree

1 file changed

1 file changed

`‎jsonschema-core.xml`

0 commit comments