From 3401a5828ba478485babc65913ac293da446afe0 Mon Sep 17 00:00:00 2001 From: Clemens Vasters Date: Mon, 8 Jun 2026 10:27:01 +0200 Subject: [PATCH] Editorial: fix references and terminology - Add RFC6901 to normative references - Replace nonstandard 'jsonpointer instance' with 'JSON Pointer reference' - Replace hard-coded 'Example 4.1' with cross-reference anchor Fixes #1 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- draft-vasters-json-structure-import.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/draft-vasters-json-structure-import.md b/draft-vasters-json-structure-import.md index e54b914..a77f087 100644 --- a/draft-vasters-json-structure-import.md +++ b/draft-vasters-json-structure-import.md @@ -30,6 +30,7 @@ normative: RFC2119: RFC3986: RFC3987: + RFC6901: RFC8174: JSTRUCT-CORE: title: "JSON Structure Core" @@ -91,8 +92,8 @@ type that it shadows. When importing definitions into a local namespace, the processor MUST ensure that all imported cross-references are resolved within the imported definitions -themselves and not to the local schema. That means that any `jsonpointer` -instance (`$ref` or `$extends` or `$addins`) within imported definitions MUST be +themselves and not against the local schema. That means that any JSON Pointer +reference ({{RFC6901}}) (`$ref`, `$extends`, or `$addins`) within imported definitions MUST be prefixed with the local namespace under which the definitions were imported. This applies recursively to any imported schema that itself contains imports. @@ -301,7 +302,7 @@ namespace: ## Example: Using `$importdefs` to import the `definitions` section of an external schema {#example-importdefs} -The external schema remains the same as in Example 4.1. +The external schema remains the same as in {{example-import-external-schema}}. The importing schema uses `$importdefs` to import the `definitions` section of the external schema into the "People" namespace. The imported `Address` type is then