> Whether or not you think this is a good design, it's clearly
> an example of
> an XML application taking advantage of those distinctions for element
> content defined to represent a number.
Interesting. Of course, in another context, those three syntactic devices
might be interpreted differently.
The example you gave seems like an evil method for data hiding, rather than
a meaningful interpretation of syntax. Would it have been any harder just
to enumerate the three cases you mentioned and give them meaningful string
representations in XML? I think not.
