You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 2, 2023. It is now read-only.
Copy file name to clipboardExpand all lines: learn/glossary.md
+28Lines changed: 28 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -14,6 +14,18 @@ If you encounter a term you wish were defined here, please feel free to [file an
14
14
15
15
The entries on this page can be linked to via anchor links (e.g. `https://json-schema.org/learn/glossary.html#vocabulary`) when sharing a definition with others.
16
16
17
+
### dialect
18
+
19
+
A cohesive collection of [keywords](#keyword) available for use within a schema, often representing a use-case specific single release of the JSON Schema specification.
20
+
21
+
Dialects, particularly the 2019-09 and 2020-12 dialects, are often defined via a collection of [vocabularies](#vocabulary).
22
+
23
+
Each dialect is identified by a URI, its *dialect identifier*, which [schemas](#schema) may then reference in their `$schema`[keyword](#keyword).
24
+
Doing so identifies the schema as being written in the dialect, and thereby indicates which keywords are usable within it, along with their intended meaning.
25
+
26
+
The JSON Schema specification defines a number of dialects, each of which enable vocabularies suitable for the dialect's specific use case.
27
+
These vocabularies are [described](https://json-schema.org/specification.html#general-purpose-meta-schema) in meta-schemas.
28
+
17
29
### draft
18
30
19
31
An individual release of the JSON Schema specification.
@@ -70,3 +82,19 @@ The rules constituting which schemas are conformant, as well as the rules govern
70
82
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.
71
83
72
84
In recent [drafts](#draft) of the specification, a schema is either a JSON object or a JSON boolean value.
85
+
86
+
### vocabulary
87
+
88
+
A tightly related collection of [keywords](keyword), grouped to facilitate re-use.
89
+
90
+
A vocabulary is specified by a prose document or specification which explains the semantics of its keywords in a way suitable for implementers and users of the vocabulary.
91
+
It often also includes a [meta-schema](#meta-schema) (or multiple metaschemas) which define the syntax of its keywords.
92
+
93
+
Anyone can create and publish a vocabulary, and implementations generally will include facilities for extending themselves with support for additional vocabularies and their keywords.
94
+
The JSON Schema specification includes a number of vocabularies which cover each of the keywords it defines.
95
+
96
+
In some [dialects](#dialect) of JSON Schema, the `$vocabulary` keyword can be used to include the keywords defined by a vocabulary into the dialect, as well as to indicate whether implementations must specifically recognize the vocabulary in order to be able to process schemas written in the dialect or not.
97
+
98
+
#### See also
99
+
100
+
*[`json-schema-vocabularies`](https://github.com/json-schema-org/json-schema-vocabularies), a repository which collects known third-party JSON Schema vocabularies
0 commit comments