W3C home > Mailing lists > Public > public-swbp-wg@w3.org > October 2004

hexBinary & base64Binary comparisons

From: Ashok Malhotra <ashok.malhotra@oracle.com>
Date: Tue, 5 Oct 2004 07:47:54 -0700
To: Michael Kay <mhk@mhk.me.uk>, Jeremy Carroll <jjc@hplb.hpl.hp.com>
CC: w3c-xml-query-wg@w3.org, w3c-xsl-wg@w3.org, SWBPD list <public-swbp-wg@w3.org>
Message-ID: <20041005074754742.00000004020@amalhotr-pc>

We discussed this and instead of allowing comparison operators
the WGs decided to allow casting from one type to another.
So, you have cast and then compare. 

All the best, Ashok


-----Original Message-----
From: w3c-xml-query-wg-request@w3.org
[mailto:w3c-xml-query-wg-request@w3.org]On Behalf Of Michael Kay
Sent: Tuesday, October 05, 2004 5:46 AM
To: 'Jeremy Carroll'; 'Ashok Malhotra'
Cc: w3c-xml-query-wg@w3.org; w3c-xsl-wg@w3.org; 'SWBPD list'
Subject: RE: Request for help with semantics of XML Schema Datatypes



> Another one of the surprises for me was that hexEncodedBinary and 
> base64EncodedBinary always compare not equal, even if the binary that 
> has been encoded is the same. Is this still being worked on? Or has 
> there been a WG decision on that?

They don't "compare not equal", they are non-comparable: (b eq h) is an
error. 

No logic to it, it's just that no-one has found the time or energy to do any
work on these two types.

Michael Kay
Received on Tuesday, 5 October 2004 14:48:42 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:17:13 GMT