Ben Hutton

I really don't want to create two classes of tools. We already have a huge "this tooling doens't support that part of the spec" issue. **I'm strongly in favour of...

It's not identical. The list of exceptions are different and specifically related to the vocabulary, hence being a subsection.

@karenetheridge I had a quick look but coudln't find anything relating to this, closed or otherwise. If you find anything, let us know.

While the first part of the change makes senes, I'm not sure the "mission" part does right now. I'll move the first part of this PR to a new PR,...

Closed in favour of https://github.com/json-schema-org/json-schema-org.github.io/pull/487

Coming here to note that I'd also value "replaced". In terms of making such an change having as least friction as possible, allowing both seems like a viable solution with...

Closing this issue as we have since ingested all the site content and include it as part of our reference documentation.

I don't think the test data file wasn't designed to be used for forming the test queries. Having said that, there's no reason we couldn't provide both an import file...

How would that information be used? What's the Use Case for wanting this?

@buske @fschiettecatte Any further thoughts on this? I could see it may be useful for development purposes, but otherwise, how could it be displayed to the end user and under...