Skip to content

Commit a0c4a67

Browse files
committed
Add glossary entries for keyword and meta-schema.
1 parent cdb3858 commit a0c4a67

File tree

1 file changed

+15
-0
lines changed

1 file changed

+15
-0
lines changed

learn/glossary.md

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,12 @@ 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+
### keyword
28+
29+
A property appearing within a [schema](#schema) object.
30+
31+
The [JSON Schema specification](https://json-schema.org/specification.html) defines behavior for a large library of keywords which can be used to describe [instances](#instance).
32+
2733
### instance
2834

2935
A piece of JSON data which is to be validated by a [schema](#schema).
@@ -33,6 +39,15 @@ JSON Schema can be used to validate JSON values of any type (as well as values f
3339
The JSON Schema specification makes no broad assumptions about the structure of instances themselves beyond those of the JSON specification itself.
3440
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.
3541

42+
### meta-schema
43+
44+
A [schema](#schema) which is itself intended to describe other *schemas*.
45+
46+
JSON Schema defines a language for describing any [instance](#instance) using a schema written in JSON.
47+
Since schemas are themselves JSON values, they may be opaquely treated as *instances*, and therefore described by other schemas.
48+
49+
We refer to the schema-of-a-schema as a "meta-schema" to express this use.
50+
3651
### normative
3752

3853
In the context of JSON Schema, and formal specifications more broadly, a document which outlines standardized behavior.

0 commit comments

Comments
 (0)