[Home] [By Thread] [By Date] [Recent Entries]

  • From: Michael Kay <mike@s...>
  • To: John Cowan <johnwcowan@g...>
  • Date: Mon, 11 Aug 2014 15:17:27 +0100


On 11 Aug 2014, at 14:37, John Cowan <johnwcowan@g...> wrote:


On Mon, Aug 11, 2014 at 7:37 AM, Michael Kay <mike@s...> wrote:

the conversion to/from base64Binary lexical representation (or hexBinary lexical representation) is done by the XML parser/validator/serializer

Where are such parsers and serializers to be found?


In XDM (following XSD) the value space of a value of type xs:base64Binary is "sequence of octets", and of course it is implementation-dependent how this is represented internally. But any processor that wants to do any computation on the value is likely to represent it internally as something like byte[]. It's then the process of validation or atomization (taking the typed value of a node) which converts from the base64 representation to the internal representation, and serialization (or casting to string) which converts back to the base64 representation.

Of course a conformant processor COULD use a base64 representation internally if it chose; or indeed a base79 representation.

Michael Kay
Saxonica





[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member