Re: Some comments on the 1.1 draft
Eric van der Vlist wrote: > Michael Rys wrote: > > > Sorry but my use case is not serializing arbitrary binary data, but > > arbitrary TEXT data according to the originating type system (such as a > > database or a C#, C++, Java etc based webservice). Unfortunately, such > > TEXT properties may contain control characters, since the originating > > type system does not preclude them. Requiring people to base 64 encode > > TEXT just to deal with the 0.1% of cases where control characters may > > appear seems to be problematic. > > > The problem seems to be that this TEXT doesn't enter into the definition > of text made in XML 1.0, but it should be possible to represent it > differently using what we have at hand. Isn't that what character references are for? You already need to escape characters such as single and/or double quotes, < & etc, so adding a few numbers to a case statement doesn't seem to be a huge deal. Jonathan
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format