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 27742 - xs:anyURI validation
Summary: xs:anyURI validation
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XQuery 3 & XPath 3 Test Suite (show other bugs)
Version: Working drafts
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: O'Neil Delpratt
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-04 15:06 UTC by Benito van der Zander
Modified: 2015-02-10 13:40 UTC (History)
1 user (show)

See Also:

Attachments

Description Benito van der Zander 2015-01-04 15:06:49 UTC 
There are a few tests (K2-SeqExprCastable-6, K2-SeqExprCastable-7, K2-SeqExprCast-210, K2-SeqExprCast-422, K2-SeqExprCast-423, K2-SeqExprCast-424, K2-SeqExprCast-505 ) that expect some restrictions on the xs:anyURI values and do not have a XSD1.0 dependency.

However, in  functions and operators it says:

>1 Introduction
>XSD1.1 ... allows any character string to appear as the value of an xs:anyURI item. 


>18.2 Casting from xs:string and xs:untypedAtomic
>For xs:anyURI, the extent to which an implementation validates the lexical form of xs:anyURI is ·implementation dependent·.


So it seems reasonable to  allow any string as anyURI
Comment 1 Michael Kay 2015-02-10 13:33:06 UTC 
The WG agreed that we should add a dependency on XSD 1.0 for these tests. (And optionally add an XSD 1.1 variant of the test if this seems useful).
Comment 2 O'Neil Delpratt 2015-02-10 13:40:38 UTC 
Fix and committed to cvs.