W3C home > Mailing lists > Public > public-qt-comments@w3.org > September 2017

[Bug 30180] [xslt30ts] Test case error-0905a - invalid xs:anyURI

From: <bugzilla@jessica.w3.org>
Date: Tue, 12 Sep 2017 17:39:23 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-30180-523-u1rRSP9u8A@http.www.w3.org/Bugs/Public/>

Abel Braaksma <abel.braaksma@xs4all.nl> changed:

           What    |Removed                     |Added
                 CC|                            |abel.braaksma@xs4all.nl

--- Comment #2 from Abel Braaksma <abel.braaksma@xs4all.nl> ---
Interestingly, in FO31 the spec writes:

    « For xs:anyURI, the extent to which an implementation validates the
    form of xs:anyURI is ·implementation-dependent·.»

Not sure if the difference was intentional.

FO31 is more lenient than XSD11, it doesn't mention the XML Char limitation. 

Perhaps we should add for XTDE0905 that raising this error is implementation
dependent, unless it is "http://www.w3.org/2000/xmlns/".

I also found that in 5.8 we say about Uri References:

    « [Definition: Within this specification, the term URI Reference, unless 
    otherwise stated, refers to a string in the lexical space of the xs:anyURI 
    datatype as defined in [XML Schema Part 2].] Note that this is a wider 
    definition than that in [RFC3986]»

which doesn't seem to mention XSD 1.1, nor the leniency of xs:anyURI validation
in FO31.

If we could, I would prefer that we follow FO31 in making any and all URI
References and xs:anyURI mentions implementation-dependent with respect to
validation of the validity of the URI (per RFC or per XSD).

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 12 September 2017 17:39:25 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 12 September 2017 17:39:26 UTC