W3C home > Mailing lists > Public > public-qt-comments@w3.org > May 2003

RE: F&O Casting from binary types to xs:boolean

From: Paul Cotton <pcotton@microsoft.com>
Date: Tue, 13 May 2003 12:54:12 -0400
Message-ID: <E7AC4500EAB7A442ABA7521D1881439706324DA7@tor-msg-01.northamerica.corp.microsoft.com>
To: "Priscilla Walmsley" <priscilla@walmsley.com>
Cc: <public-qt-comments@w3.org>

> I'm not sure why someone would need to cast hexBinary and base64Binary
> to boolean,

We agree and have decided to remove this functionality from the F&O
document.

/paulc

Paul Cotton, Microsoft Canada 
17 Eleanor Drive, Nepean, Ontario K2E 6A3 
Tel: (613) 225-5445 Fax: (425) 936-7329 
mailto:pcotton@microsoft.com

  

> -----Original Message-----
> From: public-qt-comments-request@w3.org [mailto:public-qt-comments-
> request@w3.org] On Behalf Of Priscilla Walmsley
> Sent: May 10, 2003 7:44 AM
> To: public-qt-comments@w3.org
> Subject: F&O Casting from binary types to xs:boolean
> 
> 
> I'm not sure why someone would need to cast hexBinary and base64Binary
> to boolean, but of course there may be a use case I haven't thought
of.
> However, the casting rule is a little unclear.  It says:
> 
> "If ST is xs:base64Binary or xs:hexBinary and SV is " 1 ", then TV is
> true; if ST is xs:base64Binary or xs:hexBinary and SV is " 0 ", then
TV
> is false."
> 
> 
> 1. Putting the values " 1 " and " 0 "  in quotes implies that these
are
> valid lexical forms for these types.  They aren't, since these values
> must come in octets.  Was the intention that hexBinary "01" be cast to
> boolean true?  What about hexBinary "0001" ?
> 
> 2. What if the value is not equivalent to 0 or 1?  It doesn't say
> whether it should be cast to true, raise an error, or what.
> 
> Thanks,
> Priscilla
Received on Tuesday, 13 May 2003 12:54:26 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 18:14:24 GMT