Jason Desrosiers

@handrews > while meta-schemas are the main rationale for those keywords, they are not the only recursive schemas. That's true. Moving to keyword-level meta-schemas doesn't make `$recursive*` completely redundant. But,...

@gregsdennis The `validation` keyword is my least favorite part of how this ended up working, but I couldn't come up with any way around it (or something like it). Let's...

@gregsdennis I've been really busy today and haven't had time to look at your last comment in detail, but I wanted to point this out ... > > If I...

@gregsdennis I'm finally getting around to reviewing how you have applied `$meta` to JSON Schema. Here's my questions/comments. It looks like you've kept the concept of a the vocabulary-level meta-schema,...

@gregsdennis By dialect (@handrews's word) I mean the top level schema. Draft 2019-09 and OAS 3.1 are two examples of dialects. At the vocabulary-schema level, `$vocabulary` is used to declare...

> > Did you mean to use the keyword-name => keyword-id mapping like in $meta? > Yeah, that's the idea. > > I'm not sure what a dialect-level meta-schema would...

@gregsdennis I like it. Allow me to iterate a bit. ### Meta-schema No changes here, but I'll point out that even tho the keywords are providing their own meta-schemas, additional...

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...

I'm still not entirely sure how I feel about the approach. I think it will work fine. I think my only concern is that we would be making a drastic...

I completely agree that it needs an update. Doing nothing is not an option. My main concern is maintaining a bunch of different versions of the output format as we...