On Tue, 15 Sep 2020 at 10:08, Florian Schmaus <[email protected]> wrote:
> On 9/14/20 9:28 PM, Sam Whited wrote: > > What escaping mechanism, the JSON one or the XML one (probably the JSON > > one to avoid weird double-escaping issues)? > > I wonder if this does matter. > > The tricky part are code points that do not need to be escaped in JSON, > but are invalid and not escapeable in XML 1.0. Those need to be escaped > in the JSON representation, as JSON allows any code point to be escaped > (RFC 7159 § 7 "Any character may be escaped"). > > I don't know if those exists. > I don't know that there are any characters that cannot be escaped in XML 1.0, are there? Besides, does it matter how they're escaped anyway if there's a choice? Once the data in pulled from XML and then from JSON, the original data will be unescaped fine, surely, whichever way it's been escaped? Maybe I just don't understand what this normative text is trying to mandate. Dave.
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
