Greg Dennis
Greg Dennis
Figured it'd be better in it's own folder than with the primary specs. The folder already existed and housed the schema file.
This makes progress toward some of what is discussed in https://github.com/json-schema-org/json-schema-spec/issues/1065. Basically, we need a place to include metadata about an evaluation. This PR wraps the existing output in a...
This is just a concept PR to get an idea of what #1078 might look like. I'm not too particular on the wording of the new core spec section, but...
_In #1434, @karenetheridge left a [comment](https://github.com/json-schema-org/json-schema-spec/pull/1434#pullrequestreview-1618682543) regarding special-casing meta-schema validations. This issue continues that conversation._ When validating a schema with a meta-schema that contains an subschema with a different `$schema`...
***IMPORTANT: This changes how meta-schemas are organized but not really how they work.*** Relevant to this discussion: - [whether optional vocabs make sense](https://github.com/orgs/json-schema-org/discussions/342) - [URI naming scheme](https://github.com/json-schema-org/json-schema-spec/issues/1401) - [adding keyword...
This discussion was split from #1391. See also #898. Historically, `integer` was added to the `type` keyword even though it's not distinguishable in JSON from `number`. Also, some time ago,...
Branching off of https://github.com/json-schema-org/json-schema-spec/issues/1401, we should discuss the idea of assigning URIs to keywords. This could enable a number of things: - keyword aliasing via custom vocabularies - keyword identification...
Since we've decided that new feature proposals will be defined in external documents, should we have a template document?
In [What current features should be considered unstable?](https://github.com/orgs/json-schema-org/discussions/472#discussioncomment-6918674) we determined that most everything available in 2020-12 will be considered stable, with some things having a few changes. This issue will...