Jason Desrosiers

> I'll have to check the RFC to be 100% sure, but I'm pretty sure a schema with an empty hash normalizes to the hash being removed. If I'm right...

>>> disallowing [fragments in $ids] resolved a confusing/undefined situation where a schema could identify itself as being at one pointer, while actually being at a different pointer in the resource...

@handrews You're right. `"id": "#/definitions/foo"` has been unambiguously invalid since draft-05 and ambiguously invalid forever (not specified as invalid, but clearly not intended use). `"id": "/schema/foo#/definitions/foo"` is more ambiguous. I've...

Honestly, I think this work is a bit premature. Our process should be discussed, agreed upon, and documented in `CONTRIBUTING.md` before we automate it. Having an assigned milestone and a...

> There's no reason why this can't go into the current draft's metaschema We generally don't consider meta-schemas living documents. Once they are released, we don't change them any more...

> We have in the past, however, fixed inconsistencies between the written spec and the metaschema, where the written spec prevails Right, which is essentially bug fixes. This is not...

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'll have to look at this in more detail later, but here's my thoughts after a quick look. Knowing applicators is useful because it gives us a way to know...

> It may not be useful to you, but for me I didn't mean to imply that wasn't useful. I just meant I hadn't had a chance to think about...

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