File tree 1 file changed +7
-3
lines changed
1 file changed +7
-3
lines changed Original file line number Diff line number Diff line change @@ -201,9 +201,7 @@ https://github.com/orgs/json-schema-org/discussions/342.)
201
201
The vocabulary URI is an opaque value. There is no data that an implementation
202
202
can reference to identify the keywords defined by the vocabulary. The vocabulary
203
203
schema _ implies_ this, but scanning a ` properties ` keyword isn't very reliable.
204
- Moreover, such a system cannot provide metadata about the keywords. As such, the
205
- user must explicitly ensure that the implementation recognizes and supports the
206
- vocabulary, which isn't much of an improvement over the current state.
204
+ Moreover, such a system cannot provide metadata about the keywords.
207
205
208
206
Having some sort of "vocabulary definition" file could alleviate this.
209
207
@@ -214,6 +212,12 @@ anyway. (Such information cannot be gleaned from a vocabulary specification. For
214
212
example, an implementation can't know what to do with a hypothetical ` minDate `
215
213
keyword.)
216
214
215
+ Several ideas have been offeree for this sort of document:
216
+
217
+ - https://github.com/json-schema-org/json-schema-spec/issues/1523
218
+ - https://github.com/json-schema-org/json-schema-spec/issues/1423
219
+ - https://github.com/json-schema-org/json-schema-spec/pull/1257
220
+
217
221
#### Implicit Inclusion of Core Vocabulary
218
222
219
223
Because the Core keywords (the ones that start with ` $ ` ) instruct an
You can’t perform that action at this time.
0 commit comments