Re: RFC: REST-RPC
John Wilson <[email protected]>
| Newsgroups | gmane.text.xml.rpc.specification |
|---|---|
| Message-ID | <[email protected]> |
On 20 Apr 2006, at 15:39, Ernst de Haan wrote:
> Officially, Unicode is not supported in XML-RPC. So if you want to be
> compatible, you should not use it. See:
> http://www.xmlrpc.com/discuss/msgReader$2129
The spec was amended in 2003 to remove the ASCII reference in the
definition of <string>. My understanding is that all conforming
implementations must accept at least UTP-8 and UTF-16 encoded Unicode
characters (i.e. they should conform to the XML spec).
There still exists a problem with the spec. This section:
'What characters are allowed in strings? Non-printable characters?
Null characters? Can a "string" be used to hold an arbitrary chunk of
binary data?
Any characters are allowed in a string except < and &, which are
encoded as < and &. A string can be used to encode binary data.'
is not possible to implement and still emit well formed XML. Only
the TAB, CR and LF control characters are allowed in XML documents
(by control character I mean Unicode characters with code points
below 0X20).
My recommendation to implementers is generally to emit XML with no
encoding declaration and to use numeric character references for
those Unicode characters with code points > 0X7F. This seems to
maximise the interoperability.
John Wilson
The Wilson Partnership
web http://www.wilson.co.uk
blog http://eek.ook.org
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/xml-rpc/
<*> To unsubscribe from this group, send an email to:
[email protected]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/