From d2b5fd80b57d0bf9b341f48ae5d952d93f09c82f Mon Sep 17 00:00:00 2001 From: Eemeli Aro Date: Tue, 27 Feb 2024 17:24:01 +0200 Subject: [PATCH] Add note about XML C0 characters adding restrictions (#681) * Add note about XML C0 characters adding restrictions * Apply suggestions from code review Co-authored-by: Addison Phillips * Update note to match NUL removal, drop XML 1.1 mention * Drop mention of "resource format" Co-authored-by: Addison Phillips --------- Co-authored-by: Addison Phillips --- spec/data-model/README.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/spec/data-model/README.md b/spec/data-model/README.md index eb35d230d..250ec9613 100644 --- a/spec/data-model/README.md +++ b/spec/data-model/README.md @@ -46,6 +46,14 @@ the JSON and DTD definitions are intended for interchange between systems and pr To that end, they relax some aspects of the data model, such as allowing declarations, options, and attributes to be optional rather than required properties. +> [!NOTE] +> Users relying on XML representations of messages should note that +> XML 1.0 does not allow for the representation of all C0 control characters (U+0000-U+001F). +> Except for U+0000 NULL , these characters are allowed in MessageFormat 2 messages, +> so systems and users relying on this XML representation for interchange +> might need to supply an alternate escape mechanism to support messages +> that contain these characters. + > [!IMPORTANT] > The data model uses the field name `name` to denote various interface identifiers. > In the MessageFormat 2 [syntax](/spec/syntax.md), the source for these `name` fields