Skip to content

Editorial: fix obsolete RFC reference and terminology #4

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
+4 −4
Merged

Editorial: fix obsolete RFC reference and terminology #4

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: 4 additions & 4 deletions draft-vasters-json-structure-units.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ author:

normative:
RFC2119:
RFC4646:
RFC5646:
RFC8174:
IEEE_260.1_2024:
author:
Expand Down Expand Up @@ -108,7 +108,7 @@ Currencies", an extension to JSON Structure Core. This specification defines a
set of annotation keywords for associating scientific unit and currency metadata
and constraints, primarily for use with numeric values.

JSON Structure Scientific Units provides a mechanism for schema authors to
This extension provides a mechanism for schema authors to
explicitly declare the unit associated with numeric data, thereby enabling
precise mapping between schema representations and external data systems.

Expand Down Expand Up @@ -193,8 +193,8 @@ array items or map values.
- The value of `symbols` MUST be a `map`.
- The keys of the `symbols` map MUST be strings that represent a purpose
indicator. The `lang:` prefix is reserved for language-specific symbols. The
suffix after the colon specifies the language code. The language code MUST
conform to the {{RFC4646}} standard.
suffix after the colon specifies the language tag. The language tag MUST
conform to BCP 47 {{RFC5646}}.
- The values of the `symbols` map MUST be strings that represent the symbol.
- The `symbols` keyword MAY be used as an annotation on any schema element.

Expand Down
Loading