Jason Desrosiers

Ahh, you're talking about using `$schema` in a document as a way to reference a schema that describes that document. That's not actually a JSON Schema thing. It's a convention...

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

> If the Applicator vocabulary isn't used to process the current schema, but the "contains" property exists in the schema object, should an implementation consider it as presented? I think...

I'm sorry I used the word "reasonable". In hind sight it sounds like a passive aggressive way to diminish other ideas. It was just the only reasonable interpretation I could...

The wording does seem confusing. I'm not sure it's wrong, but just that I'm not sure means it should be clearer.

I'm a bit tired and that part of the spec isn't fresh in my head right now, but it doesn't seem necessary for there to be that many changes. I...

> I think we do need to decide if the resources are actually split and stored as separate in-memory entities, or ... I don't think we do need to decide....

> OK, so there's really no functionality change at all here. Implementations are just as free to bleed over schema resource boundaries as before. Yes, my intention wasn't change anything,...

This is definitely confusing, because there is JSON Schema the language and JSON Schema the media type. They are two distinct things, but have the same name. JSON Schema the...

I think we should get consensus on taking this approach before putting too much effort into this.