From 7d00d7b4ad04b4752c3a1e66210a6470bf1893e3 Mon Sep 17 00:00:00 2001 From: Arnaud J Le Hors Date: Mon, 2 Nov 2026 13:06:02 +0100 Subject: [PATCH] remove normative language from informative annexes Signed-off-by: Arnaud J Le Hors --- spec.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spec.md b/spec.md index 1ce1e66..6b3bbca 100644 --- a/spec.md +++ b/spec.md @@ -3595,7 +3595,7 @@ Content inside [``](#custom) is implementation-defined and not governed To improve interoperability and reduce naming collisions, the following recommendations apply: - Producers of shared custom vocabularies SHOULD use formal XML namespaces with stable namespace URIs. -- Processors SHOULD treat the namespace URI as the namespace identifier and MUST NOT assume semantic meaning from prefix names alone. +- Processors SHOULD treat the namespace URI as the namespace identifier and SHOULD NOT assume semantic meaning from prefix names alone. - For private or local use where formal namespaces are not used, producers SHOULD use collision-resistant element names prefixed with a stable organization or project identifier (e.g. `acme_`). - Producers SHOULD avoid ambiguous generic names such as `item`, `meta`, or `data` unless these are clearly scoped by namespace or equivalent prefixing. - Producers SHOULD document custom vocabularies (intended meaning, value domains, and versioning policy) when documents are shared across tools or organizations.