Jason Desrosiers

For the URIs I use in my implementation, I drop the `$`.

How would `locationSchemas` interact with `additionalProperties`/`unevaluatedProperties`?

I don't know if the name change was intentional, but this should be considered an alternative to `propertyDependencies`. We would choose one or the other, definitely not both, so it...

Yes, there will always be outliers. In https://github.com/json-schema-org/json-schema-spec/issues/1410 someone was talking about having over 100 conditions they want to select on. I'm not worried about the performance difference mostly because...

> But this will using a little more words than using 2-tuple [propertyValue,subSchema]. That's my concern. IMO using an object rather than an array crosses the line of being too...

> Business/mgmt, who need to be convinced by their devs that an experimental feature is worth including in their code. This is critical to adoption of the experimental feature. Could...

> I propose possibly two documents: Sure. Let's try it and see how it comes out. I do think two documents is necessary, but I could have had the balance...

> Are you thinking about things like VSCode which supports 2020-12 except for `$dynamic*` (and maybe a few other bits)? Yes, that's the main thing that's for. The other reason...

> This is what I think implementations will do anyway. They'll claim support, then document that they don't support features a/b/c. You're right. Some implementations are going to do whatever...

I remembered another reason why allowing for 2024+ was important to me. It allows implementations to add support for new keywords as soon as they enter the stabilization process rather...