|
103 | 103 | This specification defines JSON Schema core terminology and mechanisms, including
|
104 | 104 | pointing to another JSON Schema by reference,
|
105 | 105 | dereferencing a JSON Schema reference,
|
106 |
| - specifying the vocabulary being used, |
| 106 | + specifying the dialect being used, |
| 107 | + specifying a dialect's vocabulary requirements, |
107 | 108 | and defining the expected output.
|
108 | 109 | </t>
|
109 | 110 | <t>
|
|
146 | 147 | some sort of condition.
|
147 | 148 | </t>
|
148 | 149 | <t>
|
149 |
| - To facilitate re-use, keywords can be organized into vocabularies. A vocabulary |
| 150 | + To facilitate re-use, keywords can be organized into vocabularies. A vocabulary |
150 | 151 | consists of a list of keywords, together with their syntax and semantics.
|
151 |
| - A set of vocabularies identified by a meta-schema is known as a dialect. |
| 152 | + A dialect is defined as a set of vocabularies and their required support |
| 153 | + identified in a meta-schema. |
152 | 154 | </t>
|
153 | 155 | <t>
|
154 | 156 | JSON Schema can be extended either by defining additional vocabularies,
|
|
1198 | 1200 | vocabularies available for use in schemas described by that meta-schema.
|
1199 | 1201 | It is also used to indicate whether each vocabulary is required or optional,
|
1200 | 1202 | in the sense that an implementation MUST understand the required vocabularies
|
1201 |
| - in order to successfully process the schema. |
| 1203 | + in order to successfully process the schema. Together, this information forms |
| 1204 | + a dialect. |
1202 | 1205 | </t>
|
1203 | 1206 | <t>
|
1204 | 1207 | The value of this keyword MUST be an object. The property names in the
|
|
0 commit comments