Skip to content

Editorial: add BCP 14 references and improve phrasing #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
clemensv merged 1 commit into from
Jun 8, 2026
+5 −3
Merged

Editorial: add BCP 14 references and improve phrasing #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions draft-vasters-json-structure-relations.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,9 @@ author:
email: clemensv@microsoft.com

normative:
RFC2119:
RFC6901:
RFC8174:
RFC8259:
RFC9562:
JSTRUCT-CORE:
Expand Down Expand Up @@ -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}

Expand Down Expand Up @@ -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.

Expand Down
Loading