Jason Desrosiers

> More specifically, how do I determine what the "dialect" is? Sorry, I didn't realize that was the question you were asking. Dialect identification works the way it always has....

> I'm not sure what you're referring to, "dialect" is new term to me. Usually we just called this the meta-schema. The term was introduced in the 2019-09 spec. >...

I really like this vision. It's very similar to where I want JSON Schema to end up. Where we disagree is that your interpretation can be applied to the current...

Historically, we haven't deprecated keywords, we've removed them. I've never really understood why we have them in the meta-schema. They are expected to not do anything, but enforce that they...

> @awwright we would need to list this in said "Keyword independence" section. Agreed. This was an oversight. I updated the PR.

@awwright > "minContains" doesn't do anything by itself [] it's technically an argument to "contains" This is not the way `minContains` and `maxContains` are defined. They assert independently. For example,...

@awwright > "requireAllExcept" is a "keyword" but it's not a validation keyword per se, it's an argument keyword: It's modifying the behavior of another (validation) keyword. This isn't correct. `requireAllExcept`...

@awwright > What makes a keyword an "argument keyword" is that a schema consisting only of e.g. `"requireAllExcept"` will never be invalid. I see what you're trying to say, but...

The `draft-next` branch has been merged and is now closed. The merge target for this PR has been changed to `main`. Here are the recommended steps to get your branch...

@gregsdennis You're right, this should probably be defined based on annotations (although I still think that approach needs to be revisited) and the current annotation behavior of `properties` is insufficient...