- From: <bugzilla@jessica.w3.org>
- Date: Tue, 12 Sep 2017 18:52:13 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=30180
--- Comment #4 from Michael Kay <mike@saxonica.com> ---
>FO31 is more lenient than XSD11, it doesn't mention the XML Char limitation.
It doesn't need to. The section you cite from (§19.2) is about casting from
xs:string, and all characters in an xs:string instance are legal XML Char's by
definition.
>« [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].]
I don't think it needs to because we have a blanket statement that processors
can choose which XSD version to support. But in any case, the definition of
"URI Reference" has no bearing on this bug.
The spec issues concerning the precise rules for namespace URIs are one of
those areas that the WG has spent a lot of time on, and spending even more time
is unlikely to sort out the mess, because the mess is inherited from other
specs. So I don't suggest we attempt it. I'm just trying to fix the test case,
which I think fairly clearly depends on which XSD version you're using.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 12 September 2017 18:52:16 UTC