Specify multi-value annotation behavior.

With the applicability/attachment concept, we now have a way
to talk about what happens when multiple annotation values
are present.  Add notes to each keyword as needed.

Author: handrews

jsonschema-validation.xml

@@ -1180,7 +1180,9 @@
 
                 <section title='"default"'>
                     <t>
-                        There are no restrictions placed on the value of this keyword.
+                        There are no restrictions placed on the value of this keyword.  When
+                        multiple occurrences of this keyword are applicable to a single
+                        sub-instance, implementations SHOULD remove duplicates.
                     </t>
                     <t>
                         This keyword can be used to supply a default JSON value associated with a
@@ -1191,13 +1193,16 @@
 
                 <section title='"readOnly"'>
                     <t>
-                        The value of this keyword MUST be a boolean.
+                        The value of this keyword MUST be a boolean.  When multiple occurrences
+                        of this keyword are applicable to a single sub-instance, the resulting
+                        value MUST be true if any occurrence specifies a true value, and MUST
+                        be false otherwise.
                     </t>
                     <t>
-                        If it has a value of boolean true, this keyword indicates that the value of the
-                        instance is managed exclusively by the owning authority, and attempts by an
-                        application to modify the value of this property are expected to be ignored or
-                        rejected by that owning authority.
+                        If it has a value of boolean true, this keyword indicates that the value
+                        of the instance is managed exclusively by the owning authority, and
+                        attempts by an application to modify the value of this property are
+                        expected to be ignored or rejected by that owning authority.
                     </t>
                     <t>
                         For example, this property would be used to mark a database-generated serial
@@ -1215,19 +1220,21 @@
                     <t>
                         The value of this keyword MUST be an array.
                         There are no restrictions placed on the values within the array.
+                        When multiple occurrences of this keyword are applicable to a single
+                        sub-instance, implementations MUST provide a flat array of all
+                        values rather than an array of arrays.
                     </t>
                     <t>
                         This keyword can be used to provide sample JSON values associated with a
                         particular schema, for the purpose of illustrating usage.  It is
                         RECOMMENDED that these values be valid against the associated schema.
                     </t>
                     <t>
-                        Implementations MAY use the value of "default", if present, as
+                        Implementations MAY use the value(s) of "default", if present, as
                         an additional example.  If "examples" is absent, "default"
                         MAY still be used in this manner.
                     </t>
                 </section>
-
             </section>
         </section>