|
276 | 276 | </section>
|
277 | 277 |
|
278 | 278 | <section title='The "$schema" keyword'>
|
279 |
| - <section title="Purpose"> |
280 |
| - <!-- TODO a custom $schema keyword might also be used to enforce minimum required functionality of a validator --> |
281 |
| - <t> |
282 |
| - The "$schema" keyword is both used as a JSON Schema version identifier and the |
283 |
| - location of a resource which is itself a JSON Schema, which describes any schema |
284 |
| - written for this particular version. |
285 |
| - </t> |
286 |
| - <t> |
287 |
| - The root schema of a JSON Schema document SHOULD use this keyword. |
288 |
| - The value of this keyword MUST be a <xref target="RFC3986">URI</xref> (an "absolute" URI), |
289 |
| - and this URI MUST be normalized. |
290 |
| - The current schema MUST be valid against the meta-schema identified by this URI. |
291 |
| - </t> |
292 |
| - <t> |
293 |
| - Values for this property are defined in other documents and by other parties. |
294 |
| - JSON Schema implementations SHOULD implement support for current and previous published drafts |
295 |
| - of JSON Schema vocabularies as deemed reasonable. |
296 |
| - </t> |
297 |
| - </section> |
298 |
| - |
| 279 | + <!-- TODO a custom $schema keyword might also be used to enforce minimum required functionality of a validator --> |
| 280 | + <t> |
| 281 | + The "$schema" keyword is both used as a JSON Schema version identifier and the |
| 282 | + location of a resource which is itself a JSON Schema, which describes any schema |
| 283 | + written for this particular version. |
| 284 | + </t> |
| 285 | + <t> |
| 286 | + The root schema of a JSON Schema document SHOULD use this keyword. |
| 287 | + The value of this keyword MUST be a <xref target="RFC3986">URI</xref> (an "absolute" URI), |
| 288 | + and this URI MUST be normalized. |
| 289 | + The current schema MUST be valid against the meta-schema identified by this URI. |
| 290 | + </t> |
| 291 | + <t> |
| 292 | + Values for this property are defined in other documents and by other parties. |
| 293 | + JSON Schema implementations SHOULD implement support for current and previous published drafts |
| 294 | + of JSON Schema vocabularies as deemed reasonable. |
| 295 | + </t> |
299 | 296 | </section>
|
300 | 297 |
|
301 | 298 | <section title="Schema references with $ref">
|
|
0 commit comments