|
301 | 301 | written for this particular version. |
302 | 302 | </t> |
303 | 303 | <t> |
304 | | - The root schema of a JSON Schema document SHOULD use this keyword. |
305 | 304 | The value of this keyword MUST be a <xref target="RFC3986">URI</xref> |
306 | 305 | (containing a scheme) and this URI MUST be normalized. |
307 | 306 | The current schema MUST be valid against the meta-schema identified by this URI. |
308 | 307 | </t> |
| 308 | + <t> |
| 309 | + The "$schema" keyword SHOULD be used in a root schema. |
| 310 | + It MUST NOT appear in subschemas. |
| 311 | + </t> |
| 312 | + <t> |
| 313 | + <cref>While this pattern is likely to remain best practice for schema authoring, implementation behavior is subject to be revised or liberalized in future drafts.</cref> |
| 314 | + </t> |
309 | 315 | <t> |
310 | 316 | Values for this property are defined in other documents and by other parties. |
311 | 317 | JSON Schema implementations SHOULD implement support for current and previous published drafts |
|
0 commit comments