Greg Dennis

Our `.gitignore` is getting pretty specific. Would it be possible to output all of the files to a specific folder so that we can just ignore that folder? Additional context:...

This is very similar to my `uniqueKeys` keyword. https://docs.json-everything.net/schema/vocabs/array-ext/#uniquekeys

We have introduced a process for new features going forward. Please have a look at that to set expectations. Also, know that we're just looking to publish existing features (in...

The process is defined in the [PROCESS.md](https://github.com/json-schema-org/json-schema-spec/blob/main/PROCESS.md) file in the root of this repository. @benjagm can you provide a link to the roadmap in its current form, please? (We also...

The output schema defines `error` because errors are only strings. It doesn't define a subschema for `annotation` because annotations can be of any value.

I see your point. Intentionality is worth something. I'll go ahead and reopen this, but it'll be for an errata correction. I'm not sure how to make that change since...

Thanks for submitting this. > Some of my schemas had cyclic refs which used to work, but now trigger stackoverflows. All of the tests that I have passed through that...

I think the primary issue I've had with recursive references is figuring out a termination condition. Currently they're just not supported, as mentioned in the [docs](https://docs.json-everything.net/schema/datagen/schema-datagen/) (yellow warning note).

Another style consideration is that in several places, we add requirements on schema authors, e.g. "Schema authors SHOULD NOT use pointers that cross resource boundaries." Would it be better to...

> a lot of the benefit of JSON Schema results when interoperability is achieved That's absolutely correct. We should minimize what we leave undefined. A specification defines a set of...