Re: [xml-dev] Proposed requirements on solutions that convertXML-illegal

[Timothy Cook <timothywayne.cook@gmail.com>]

On Thu, Apr 27, 2017 at 4:52 AM, Mukul Gandhi <gandhi.mukul@gmail.com> wrote:

Before agreeing to Mr. Timothy's post, I forgot to brush up what is really meant by the XSD type xs:string. If we look at xs:string definition at, https://www.w3.org/TR/xmlschema-2/#string it says

"The string datatype represents character strings in XML. The ·value space· of string is the set of finite-length sequences of characters (as defined in [XML 1.0 (Second Edition)]) that ·match· the Char production from [XML 1.0 (Second Edition)]."

While writing +1, I suspected that XSD's xs:string mirrors Java's String data type. But actually, xs:string takes its value space from XML 1.0 (Second Edition).

So the 'string representation' of NUL is that group of characters ​"\u0000" and can be included in an XML string. 

Character Range

[2]   Char   ::=   #x9 | #xA | #xD | [#x20-#xD7FF] | [#xE000-#xFFFD] | [#x10000-#x10FFFF] /* any Unicode character, excluding the surrogate blocks, FFFE, and FFFF. */

​So, what am I missing? There is a defined string representation for every Unicode character, even ones such as NUL, ACK, etc. not meant for display. ​

--

Timothy Cook