Validation: items/properties/patternProperties language changes

[awwright]

This revision is intended to simplify/clarify the behavior for the definitions of several keywords. It removes references to "child validation" which is undefined and not any special kind of validation. It reworks the properties/patternProperties definitions to simplify language regarding which instances are processed/applied against which schemas.

[handrews]

While I'm fine with finding a phrase more suitable than "child validation" (which is really just intended to mean "validation of children according to the regular process" not "special process that involves children"), I am generally opposed to this.

The process of selecting subschemas for application to child instances is critically important to the function of JSON Schema as a whole (I still think it belongs in core, honestly), and is very different, implementation-wise, from immediate validation keywords.

Whatever problem you see here (and aside from not liking the two words "child validation", I can't figure out what that problem is supposed to be), this is not the right fix.

[awwright]

@handrews I'm really not sure which distinction you're making, can you elaborate some?

If we want to make it clear which parts of the keyword value are applied/mapped to which instances, well, we just have to describe how that works.

[handrews]

If we want to make it clear which parts of the keyword value are applied/mapped to which instances, well, we just have to describe how that works.

PR #234.

[Relequestual]

I'd really much rather see #234 merged FIRST as I'm positive it's the right direction. Then we can look at this change after you've rebased if it still applies. I'm finding it hard to this change given #234