Clarify dependencies deprecation

[handrews]

It is focused on the subschema form, not the string array form.

This addresses #442.

[Anthropic]

typo 'schem'

[handrews]

Thanks! Fixed.

[pipobscure]

I find the schema form very useful. Please let's not remove it. If anything let's remove the values form.

{ "foo": { "required": [ "bar" ] } }

isn't that much worse than

{ "foo": [ "bar" ] }

but replacing the schema version with a combination of allOf/anyOf/oneOf/if/then/else is much worse.

It's much clearer than if/then/else.

Side-jibe at if/then/else: These are a bad idea to begin with, but since they are not obligatory to use, I'm fine keeping them. One reason why they are bad is that they mutate JSON-Schema from a schema to a programming language.

[epoberezkin]

@pipobscure I don't mind keeping both, although in this case it may be better to rename schema form as @handrews suggested, because "dependencies" really mean "properties that are required in case some property is present" (i.e., value form), not "an arbitrary schema to validate against" (which is better expressed with if/then implication).

Side-jibe at if/then/else: These are a bad idea to begin with, but since they are not obligatory to use, I'm fine keeping them. One reason why they are bad is that they mutate JSON-Schema from a schema to a programming language.

We had a long discussion and agreed that if/then/else is boolean implication (that can be expressed via and/or/not) rather than imperative construct. There are quite a few languages that use if/then/else syntax to mean the same as ternary in JS, and not a control flow statement.

[handrews]

@pipobscure yes this objection (raised primarily by me) was covered in excessive detail in #180.
This warning will stay in, as the point is to have the warning in the published draft for comment, but your objection is noted on the issue.

[handrews]

I'm going to merge this so that people who want to talk about why to remove or not remove dependencies will comment in the issue and not here. I'll leave the issue open though- I put it in the "future" milestone.