> But if the Data Model were saying that 0 and 1 are not simply 
> "string representations" (note that I didn't use '0' and '1' 
> in my previous example but just 0 and 1 -- that is not the 
> strins '0' and '1') but that 0 and 1 are *the* two xs:boolean 
> constants,
> 
> then
> 
> it would make difference as the result of evaluating a 
> boolean expression would be not a "representation" but a real 
> (or native, or genuine) boolean value.
> 
> Isn't it natural for a type to have its own genuine values 
> and not only a "representation"?

The boolean type does have its own genuine values. There are two of
these values, and they are delivered by the functions true() and
false().

I really can't see how choosing integers to represent these values helps
matters.

Michael Kay


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list