Hi folks, Sorry for dragging up an old thread (archive link for those who need it: https://mail.jabber.org/pipermail/standards/2019-February/035796.html ).
I'd like to get XEP-0335 moved on, but got stuck on encoding discussions. > It would be good if the specification noted the incompatibility between JSON > and XML definitions of what a character is, and certain characters MUST be > escaped be escaped via JSON escaping to be valid XML. Does the following resolve everyone's issues? (specifically Jonas and Waqas) - Remove this sentence from the XEP: "The data MUST be encoded as UTF-8 (though officially unspecified, this is the de facto encoding for JSON today)." - Add the following sentence: "If the JSON data contains any characters that are unrepresentable in XML 1.0, these characters MUST be escaped in the JSON data." I will also incorporate some text clarifying that one container element must contain precisely one JSON value, to address Martin's feedback, and update the RFC reference from RFC 4627 to RFC 7159. If anyone has objections or additions to the above, I'd greatly appreciate some suggested text accompanying them :) Regards, Matthew _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
