From d84ccb353c2f3ff6a08bc8c16b6435ab58a6bf31 Mon Sep 17 00:00:00 2001 From: Clemens Vasters Date: Mon, 8 Jun 2026 10:29:28 +0200 Subject: [PATCH] Editorial: fix obsolete RFC reference and terminology - Update RFC4646 to RFC5646 (BCP 47) in references block - Use correct term 'language tag' instead of 'language code' in symbols section - Broaden abstract opening (extension covers symbols/currencies too) Fixes #3 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- draft-vasters-json-structure-units.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/draft-vasters-json-structure-units.md b/draft-vasters-json-structure-units.md index 3c1686b..633ebcd 100644 --- a/draft-vasters-json-structure-units.md +++ b/draft-vasters-json-structure-units.md @@ -29,7 +29,7 @@ author: normative: RFC2119: - RFC4646: + RFC5646: RFC8174: IEEE_260.1_2024: author: @@ -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. @@ -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.