From 0b08ab58579ef976541b80138bc8190a3affa3b7 Mon Sep 17 00:00:00 2001 From: Clemens Vasters Date: Mon, 8 Jun 2026 10:28:50 +0200 Subject: [PATCH] Editorial: add BCP 14 references and improve phrasing - Add RFC2119 and RFC8174 to normative references (required for MUST/MAY usage) - Improve phrasing of identity keyword description - Fix modal placement: 'MUST only be used' -> 'MUST be used only' Fixes #1 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- draft-vasters-json-structure-relations.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/draft-vasters-json-structure-relations.md b/draft-vasters-json-structure-relations.md index 2dc4e00..24d838c 100644 --- a/draft-vasters-json-structure-relations.md +++ b/draft-vasters-json-structure-relations.md @@ -26,7 +26,9 @@ author: email: clemensv@microsoft.com normative: + RFC2119: RFC6901: + RFC8174: RFC8259: RFC9562: JSTRUCT-CORE: @@ -72,8 +74,8 @@ The key concepts introduced are: # Identity {#identity} The `identity` keyword is used to declare which properties of an object or tuple -uniquely identify instances of that type. The identity declaration functions -similarly to a primary key in relational databases. +uniquely identify instances of that type. The identity declaration serves much +like a primary key in a relational database. ## The `identity` Keyword {#identity-keyword} @@ -142,7 +144,7 @@ types. ## The `relations` Keyword {#relations-keyword} -The `relations` keyword MUST only be used with schemas of type `object` or +The `relations` keyword MUST be used only with schemas of type `object` or `tuple`. Its value MUST be a JSON object where each key is a relation name and each value is a relation declaration.