Jason Desrosiers

There are tests for initial resolution. https://github.com/json-schema-org/JSON-Schema-Test-Suite/blob/main/tests/draft2020-12/dynamicRef.json#L259 https://github.com/json-schema-org/JSON-Schema-Test-Suite/blob/main/tests/draft2020-12/dynamicRef.json#L311 There should probably be a test for using a JSON Pointer in a dynamic reference. Using a JSON Pointer doesn't make sense...

I like the general idea. It's similar to something I've proposed in the past except that I decouple keywords from vocabularies more (without eliminating the concept of vocabularies). But, this...

A few things about this proposal aren't making sense to me yet. > This project aims to develop a tool that generates mock API endpoints based on JSON Schema definitions...

> The tool would use OpenAPI to define the endpoints and JSON Schema to define the request and response bodies. Ok, that makes sense now, but there are already several...

This is a great idea. Since this is such an important and time consuming role, I wonder if it's possible to offer some compensation even if small from our open...

Having the same identifier for multiple schemas is non-sense. It's like having JSON with duplicate keys (`{ "a": 1, "a": 2 }` what is the value of `a`?). Just like...

This is a breaking change. I think that means it should have a TSC discussion and vote to decide if we're ok with that. Henry's added that before we decided...

Sorry, I misread the text you quoted. I thought the change was making it a MUST.

@benjagm Are you sure you meant to close this? We do have a meeting on the calendar for Nov 18.

I'm sympathetic to the problem you're trying to solve. It's definitely a real problem that I'd love to have a solution for. Unfortunately, I don't see any of these suggestions...