The following minor editorial issues were found during review:
1. Missing RFC6901 in normative references
The draft discusses JSON Pointer semantics but RFC6901 is not listed in the normative references metadata block.
2. Nonstandard term "jsonpointer instance"
The text refers to "any jsonpointer instance (or or ``)" — this should use the standard term "JSON Pointer reference" with a citation to RFC 6901.
3. Hard-coded "Example 4.1" reference
The text says "The external schema remains the same as in Example 4.1." — this should use an internal cross-reference anchor (e.g., {{example-import-external-schema}}) to avoid breakage if examples are reordered.
The following minor editorial issues were found during review:
1. Missing RFC6901 in normative references
The draft discusses JSON Pointer semantics but
RFC6901is not listed in the normative references metadata block.2. Nonstandard term "jsonpointer instance"
The text refers to "any
jsonpointerinstance (oror ``)" — this should use the standard term "JSON Pointer reference" with a citation to RFC 6901.3. Hard-coded "Example 4.1" reference
The text says "The external schema remains the same as in Example 4.1." — this should use an internal cross-reference anchor (e.g.,
{{example-import-external-schema}}) to avoid breakage if examples are reordered.