link to annotation requirements; add requirements of output specs to include details for errors and annotations

Author: gregsdennis

jsonschema-core.md

@@ -2124,6 +2124,10 @@ Errors are textual representations of individual validation failures, often
 intended for human consumers. This specification contains no requirements for
 the content of these errors.
 
+Output specifications which include errors SHOULD be written such that the
+sources (schema and instance) of a given error is easily identifiable and SHOULD
+use the terms defined by this document to do so.
+
 ### Annotations
 
 Many keywords are defined to produce annotations, whether intended for
@@ -2132,6 +2136,10 @@ inter-keyword communication (e.g. between `properties` and
 `readOnly`). Annotation values may be of any type and are defined by the
 keywords that produced them.
 
+Output specifications which include annotations SHOULD be written such that they
+can be easily associated with the data defined in {{collect}} and SHOULD use the
+terms defined by this document to do so.
+
 ### Dropped Annotations
 
 A dropped annotation is any annotation produced and subsequently dropped by the
@@ -2146,6 +2154,10 @@ as their default behavior. Dropped annotations SHOULD only be included when the
 implementation is explicitly configured to do so or if the implementation is
 specifically intended to be used as a debugging tool.
 
+Output specifications which include dropped annotations SHOULD be written such
+that they can be easily associated with the data defined in {{collect}} and
+SHOULD use the terms defined by this document to do so.
+
 ## Security Considerations {#security}
 
 Both schemas and instances are JSON values. As such, all security considerations