|
655 | 655 | Typically, applicator keywords are processed until a schema object with no
|
656 | 656 | applicators (and therefore no subschemas) is reached. The appropriate
|
657 | 657 | location in the instance is evaluated against the assertion and
|
658 |
| - annotation keywords in the schema object, and their results are gathered |
659 |
| - into the parent schema according to the rules of the applicator. |
| 658 | + annotation keywords in the schema object. The interactions of those |
| 659 | + keyword results to produce the schema object results are governed by |
| 660 | + section <xref target="annot-assert" format="counter"></xref>, while the |
| 661 | + relationship of subschema results to the results of the applicator |
| 662 | + keyword that applied them is described by section |
| 663 | + <xref target="applicators" format="counter"></xref>. |
660 | 664 | </t>
|
661 | 665 | <t>
|
662 | 666 | Evaluation of a parent schema object can complete once all of its
|
|
811 | 815 | assertion conditions of their own.
|
812 | 816 | </t>
|
813 | 817 | <t>
|
814 |
| - <xref target="annotations">Annotation</xref> results are |
815 |
| - preserved along with the instance location and the location of |
816 |
| - the schema keyword, so that applications can decide how to |
817 |
| - interpret multiple values. |
| 818 | + <xref target="annotations">Annotation</xref> results from subschemas |
| 819 | + are preserved in accordance with section |
| 820 | + <xref target="collect" format="counter"></xref> so that applications |
| 821 | + can decide how to interpret multiple values. Applicator keywords |
| 822 | + do not play a direct role in this preservation. |
818 | 823 | </t>
|
819 | 824 | <section title="Referenced and Referencing Schemas" anchor="referenced">
|
820 | 825 | <t>
|
|
935 | 940 | for failing schemas.
|
936 | 941 | </t>
|
937 | 942 |
|
938 |
| - <section title="Collecting Annotations"> |
| 943 | + <section title="Collecting Annotations" anchor="collect"> |
939 | 944 | <t>
|
940 | 945 | Annotations are collected by keywords that explicitly define
|
941 | 946 | annotation-collecting behavior. Note that boolean schemas cannot
|
|
1058 | 1063 | schema locations.
|
1059 | 1064 | </t>
|
1060 | 1065 | </section>
|
1061 |
| - <section title="Annotations and Assertions"> |
| 1066 | + <section title="Annotations and Assertions" anchor="annot-assert"> |
1062 | 1067 | <t>
|
1063 | 1068 | Schema objects that produce a false assertion result MUST NOT
|
1064 | 1069 | produce any annotation results, whether from their own keywords
|
|
1093 | 1098 | is kept, as the instance passes the string type assertions.
|
1094 | 1099 | </t>
|
1095 | 1100 | </section>
|
1096 |
| - <section title="Annotations and Applicators"> |
1097 |
| - <t> |
1098 |
| - In addition to possibly defining annotation results of their own, |
1099 |
| - applicator keywords aggregate the annotations collected in their |
1100 |
| - subschema(s) or referenced schema(s). |
1101 |
| - </t> |
1102 |
| - </section> |
1103 | 1101 | </section>
|
1104 | 1102 | </section>
|
1105 | 1103 | <section title="Reserved Locations">
|
|
0 commit comments