This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 3667 - Missing xs:anyUri from fn:boolean typing rule.
Summary: Missing xs:anyUri from fn:boolean typing rule.
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Formal Semantics 1.0 (show other bugs)
Version: Candidate Recommendation
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Jerome Simeon
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-07 14:43 UTC by Tim Mills
Modified: 2006-10-19 19:53 UTC (History)
0 users

See Also:

Attachments

Description Tim Mills 2006-09-07 14:43:50 UTC 
In:

http://www.w3.org/TR/xpath20/#id-ebv

"If its operand is a singleton value of type xs:string, xs:anyURI, xs:untypedAtomic, or a type derived from one of these, fn:boolean returns false if the operand value has zero length; otherwise it returns true."

However, in:

http://www.w3.org/TR/xquery-semantics/#sec_fn_boolean

statEnv |-  Type <: (empty | NodeType+ | xs:boolean | xs:string | xs:untypedAtomic | fs:numeric)
---------------------------------------------------
statEnv  |-  (FN-URI,"boolean")(Type) : xs:boolean

This typing rule should include xs:anyURI.
Comment 1 Jerome Simeon 2006-09-19 15:25:30 UTC 
Good catch. The typing rule should have xs:anyURI added to it, as follows:

statEnv |-  Type <: (empty | NodeType+ | xs:boolean | xs:string |
xs:untypedAtomic | fs:numeric | xs:anyURI)
---------------------------------------------------
statEnv  |-  (FN-URI,"boolean")(Type) : xs:boolean

- Jerome
Comment 2 Jerome Simeon 2006-09-26 14:01:21 UTC 
Tim,
The XSLT and XML Query Working groups have adopted your proposal and
will make the corresponding changes in the next version of the formal
semantics documents.
Best regards,
- Jerome Simeon
on behalf of the XSLT and XML Query WGs