 |
|
|
You might like to make a distinction between
* The characters that XML can directly represent in a particular encoding
* The characters that XML require references for in a particular encoding
* The characters that cannot be represented in XML at all
* The characters that an information item that has been given the type
xs:String can contain, for example
in a DOM.
So you could, in a DOM, AFAIK, have a string containing the character
U+0001. And you could
give it, by some process, the type xs:String. I don't know that that
would go against the definition of
String in XSD, actually. But when you came to serialize it, there
should be a problem.
Cheers
Rick Jelliffe
|
|
| |
These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.
| |
| |
|
|
|
