Commit 784ad8b

gregsdennisnotEthan

and

authored

Clean up applicator assertion language

Co-authored-by: Ethan <133719+notEthan@users.noreply.github.com>

1 parent 20fe3e1 commit 784ad8bCopy full SHA for 784ad8b

File tree

-3

lines changed

-3

lines changed

Lines changed: 5 additions & 3 deletions

Original file line number	Diff line number	Diff line change
`@@ -601,9 +601,11 @@ the keyword's value. Alternatively, an applicator may refer to a schema`
`601`	`601`	`elsewhere in the same schema document, or in a different one. The mechanism for`
`602`	`602`	`identifying such referenced schemas is defined by the keyword.`
`603`	`603`
`604`		`-Applicator keywords also behave as assertions by defining how subschema or`
`605`		`-referenced schema boolean [assertion](#assertions) results are modified and/or`
`606`		`-combined to produce the boolean result of the applicator. Applicators may apply`
	`604`	`+Applicator keywords also behave as assertions, using the assertion results of`
	`605`	`+each subschema or referenced schema of the keyword. These boolean results are`
	`606`	+modified (e.g. the `not` keyword negates its subschema's assertion) and/or
	`607`	+combined (e.g. `allOf` takes the conjunction of its subschemas' assertions)
	`608`	`+to produce the boolean result of the applicator.`
`607`	`609`	`any boolean logic operation to the assertion results of subschemas, but SHOULD`
`608`	`610`	`NOT introduce new assertion conditions of their own.[^2]`
`609`	`611`

Comments

(0)