|
350 | 350 | and its companions, are free to define other behaviors as well.
|
351 | 351 | </t>
|
352 | 352 | <t>
|
353 |
| - A JSON Schema MAY contain properties which are not schema keywords. |
354 |
| - Unknown keywords SHOULD be treated as annotations, where the value |
355 |
| - of the keyword is the value of the annotation. |
| 353 | + A JSON Schema MAY contain properties which are not schema keywords or are not recognized as schema keywords. |
| 354 | + The behavior of such keywords is governed by section |
| 355 | + <xref target="unrecognized" format="counter"></xref>. |
356 | 356 | </t>
|
357 | 357 | <t>
|
358 | 358 | An empty schema is a JSON Schema with no properties, or only unknown
|
|
600 | 600 | by any entity. Save for explicit agreement, schema authors SHALL NOT
|
601 | 601 | expect these additional keywords and vocabularies to be supported by
|
602 | 602 | implementations that do not explicitly document such support.
|
603 |
| - Implementations SHOULD treat keywords they do not support as annotations, |
604 |
| - where the value of the keyword is the value of the annotation. |
605 | 603 | </t>
|
606 | 604 | <t>
|
607 | 605 | Implementations MAY provide the ability to register or load handlers
|
608 | 606 | for vocabularies that they do not support directly. The exact mechanism
|
609 | 607 | for registering and implementing such handlers is implementation-dependent.
|
610 | 608 | </t>
|
| 609 | + |
| 610 | + <section title="Handling of unrecognized or unsupported keywords" anchor="unrecognized"> |
| 611 | + <t> |
| 612 | + Implementations SHOULD treat keywords they do not recognize, or that |
| 613 | + they recognize but do not support, as annotations, where the value of |
| 614 | + the keyword is the value of the annotation. Whether an implementation |
| 615 | + collects these annotations or not, they MUST otherwise ignore the keywords. |
| 616 | + </t> |
| 617 | + </section> |
611 | 618 | </section>
|
612 | 619 |
|
613 | 620 | </section>
|
|
0 commit comments