Skip to content

Commit 80cd553

Browse files
committed
Clearly define a dialect
Fixes json-schema-org#1015
1 parent c4e2b99 commit 80cd553

File tree

1 file changed

+7
-4
lines changed

1 file changed

+7
-4
lines changed

jsonschema-core.xml

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -103,7 +103,8 @@
103103
This specification defines JSON Schema core terminology and mechanisms, including
104104
pointing to another JSON Schema by reference,
105105
dereferencing a JSON Schema reference,
106-
specifying the vocabulary being used,
106+
specifying the dialect being used,
107+
specifying a dialect's vocabulary requirements,
107108
and defining the expected output.
108109
</t>
109110
<t>
@@ -146,9 +147,10 @@
146147
some sort of condition.
147148
</t>
148149
<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
150151
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.
152154
</t>
153155
<t>
154156
JSON Schema can be extended either by defining additional vocabularies,
@@ -1198,7 +1200,8 @@
11981200
vocabularies available for use in schemas described by that meta-schema.
11991201
It is also used to indicate whether each vocabulary is required or optional,
12001202
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.
12021205
</t>
12031206
<t>
12041207
The value of this keyword MUST be an object. The property names in the

0 commit comments

Comments
 (0)