Skip to content
This repository was archived by the owner on Nov 2, 2023. It is now read-only.

Commit cdb3858

Browse files
authored
Merge pull request #462 from json-schema-org/instance-schema
Add glossary entries for schema and instance.
2 parents b42aa9b + 9783f12 commit cdb3858

File tree

1 file changed

+19
-0
lines changed

1 file changed

+19
-0
lines changed

learn/glossary.md

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,15 @@ While future drafts may introduce new behavior or changes to existing behavior,
2424

2525
The current list of drafts can be found [here](https://json-schema.org/specification-links.html#published-drafts).
2626

27+
### instance
28+
29+
A piece of JSON data which is to be validated by a [schema](#schema).
30+
31+
JSON Schema can be used to validate JSON values of any type (as well as values from many JSON-like formats which can be reasonably represented as JSON).
32+
33+
The JSON Schema specification makes no broad assumptions about the structure of instances themselves beyond those of the JSON specification itself.
34+
In particular it does not reserve any properties within a JSON object for its own use, or require parsers of JSON to support features beyond those already mandated of JSON implementations.
35+
2736
### normative
2837

2938
In the context of JSON Schema, and formal specifications more broadly, a document which outlines standardized behavior.
@@ -36,3 +45,13 @@ This page for instance, not being a normative document, is not able to proscribe
3645
#### See also
3746

3847
* [normative](https://developer.mozilla.org/en-US/docs/Glossary/Normative) and [non-normative](https://developer.mozilla.org/en-US/docs/Glossary/non-normative) in the Mozilla Glossary, and its links
48+
49+
### schema
50+
51+
A document, written according to the proscribed structure of the JSON Schema specification, which can be used to validate [instances](#instance).
52+
53+
The rules constituting what schemas are *valid* JSON Schemas, as well as the rules governing their behavior when validating instances, are defined by the JSON Schema specification.
54+
55+
Strictly speaking, according to the specification, schemas are themselves JSON documents, though it is somewhat common for them to be authored or maintained in other languages which are easily translated to JSON, such as YAML.
56+
57+
In recent [drafts](#draft) of the specification, a schema is either a JSON object or a JSON boolean value.

0 commit comments

Comments
 (0)