[
Lists Home |
Date Index |
Thread Index
]
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.
Elements and PIs can be used as already mentioned and other encoding
might easily be invented if hex and base64 are too verbose in this case.
Just replacing these control characters by a specific sequence
containing their names (ie "\NULL;") or their value (ie "=00") could do
the trick.
It would be a new type of encoding, less verbose than base64 or hex when
you have TEXT which is text with 0.01% of control characters and rather
easy to process...
My 0,02 Euros
Eric
--
Rendez-vous a Paris pour les Electronic Business Days 2002.
http://www.edifrance.org/ebd/index.htm
------------------------------------------------------------------------
Eric van der Vlist http://xmlfr.org http://dyomedea.com
http://xsltunit.org http://4xt.org http://examplotron.org
------------------------------------------------------------------------
|
