json-schema-spec
json-schema-spec copied to clipboard
The JSON Schema specification
When accepting JSON documents for submission, it is frequently the case the documents are objects that have at least one property that is required, such as an ID or name...
> I'm wondering if the entire concept of annotations should be revised to something different - @karenetheridge > This is the direction I'd like to go. - @jdesrosiers > I'm...
## I expect to mention "+json" structured suffix we should also cite RFC 8091 here.
With **JSON-Schema** I can flag a field or my entire document by setting the `deprecated` meta-data attribute to `true`. Besides flagging the field as deprecated I would like to add...
## I suggest to avoid normative statements in media type registration. ## Because whenever you update the spec, you need to modify the IANA registration too.
When defining an array in a json schema, I would like to be able to define the items of the array to be in ascending/descending order. ``` { "$schema": "http://json-schema.org/draft-07/schema",...
**_Context:_** In some sensitive contexts like finance, we need functionality to mask some fields in a JSON schema before exposing them to the consumer. Somehow this feature is not compatible...
## I wish to clarify whether json schema is a declarative language or > a JSON-based format for describing the structure of JSON data https://github.com/json-schema-org/json-schema-spec/blob/707431358d529dc8892610e4d8593cfdd1f090a3/jsonschema-core.xml#L63 ## note This may be...
I feel like this could be a good step forward. "Canonical URIs" is often confusing. We can simplify this by changing the language to talk about schema resource boundaries and...
I don't write objects with optional properties most of the time. I tend to prefer to use polymorphism to allow one of several data structures. When I do have an...