- From: <bugzilla@jessica.w3.org>
- Date: Tue, 03 Dec 2013 09:07:40 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23923
--- Comment #7 from Michael Dyck <jmdyck@ibiblio.org> ---
(In reply to Tim Mills from comment #5)
> (In reply to Michael Dyck from comment #2)
> > (In reply to Tim Mills from comment #0)
> >
> > > 2. More XML 1.1 problems. e.g. line-ending-Q006, where
> > > <xqx:stringConstantExpr>
> > > <xqx:value> 
 </xqx:value>
> > > </xqx:stringConstantExpr>
> > >
> > > isn't the same as ' 
 '.
> >
> > Looks the same to me. What's the problem?
>
> 
 is LINE SEPARATOR.
>
> This test is for a processor which follows the XML 1.1 line ending rules.
> Such a processor will perform line ending normalization on 
.
>
> When converted to XQueryX/XML 1.0 the &x2028; is not treated by the XML
> parser as a line ending character. It would be if it were XQuery/XML 1.1.
Ah, right, the conversion-to-XQueryX code only ever generates files with
<?xml version="1.0"?>
I suppose it could generate version="1.1" for test-cases that have
<dependency type="xml-version" value="1.1"/>
but is that enough? Could there be an XQueryX processor that only accepts 1.1
files, and so would (also) want a "1.1" version of the vast majority of
test-cases that don't have an xml-version dependency?
Or is an XQueryX processor obliged to handle input in *all* versions of XML?
The XQueryX spec doesn't seem to say explicitly, but it says:
An XQueryX processor that claims to conform to this
specification MUST implement the XQueryX syntax as defined in
4 'An XML Schema for the XQuery XML Syntax' of this specification ...
and an XML document conforms to that syntax regardless of its version decl,
right? So if "implementing the syntax" means "recognizing all instances of the
syntax", that suggests that a conforming XQueryX processor must accept input in
all versions of XML.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 3 December 2013 09:07:45 UTC