W3C home > Mailing lists > Public > public-qt-comments@w3.org > November 2005

[Bug 2545] EBV (fn:boolean) and xs:anyURI

From: <bugzilla@wiggum.w3.org>
Date: Mon, 21 Nov 2005 16:42:35 +0000
To: public-qt-comments@w3.org
Cc:
Message-Id: <E1EeEkV-0003fQ-J6@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=2545





------- Additional Comments From frans.englich@telia.com  2005-11-21 16:42 -------
  
Whether the EBV extraction of xs:anyURI("example.org/") yields a type error or  
not, I think can be concluded like this:  
  
The argument type of fn:boolean is item()*. For this reason is no atomization 
or type promotion invoked, as according to the Function Conversion Rules in 
XPath20. Thus, the body of fn:boolean is passed an xs:anyURI instance, and  
according to fn:boolean's definition xs:anyURI are not EBV-extractable and 
hence yields an error.  
  
However:  
  
* Saxon accepts "<xsl:if test="xs:anyURI('example.org')">" and evaluates it to  
true, so this is an indication in another direction.  
* Type promotion, especially involving xs:anyURI, is vague in other areas as  
well. It looks like these are editorial bugs, not design problems or  
unconsidered aspects.  
 
It will be interesting to hear what the WG members say. If one looks on prior 
cases(such as #2324), it wouldn't surprise me if EBV extraction from xs:anyURI 
should be allowed. I wonder if it makes sense though for xs:anyURI. 
 
A similar case is: http://www.w3.org/Bugs/Public/show_bug.cgi?id=2324  
  
I agree clarification would be helpful. An example involving xs:anyURI and 
fn:boolean would likely settle all confusion. 
 
  
Cheers,  
Frans
Received on Monday, 21 November 2005 16:42:46 GMT

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