- From: <bugzilla@jessica.w3.org>
- Date: Sun, 17 Mar 2013 22:43:16 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20864
Jim Melton <jim.melton@acm.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #1 from Jim Melton <jim.melton@acm.org> ---
You are quite right. One could say that this is not an error, because we
already know that it is possible to write certain XQueryX expressions that
cannot be transformed to correct XQuery expressions and that cannot be caught
by validating the XQueryX document against the XQueryX schema.
However, this problem was not difficult to fix, so I have done so.
Henceforward,
<xsd:complexType name="annotation">
<xsd:sequence>
<xsd:element name="annotationName" type="EQName"/>
<xsd:element name="arguments" type="exprList" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
is:
<xsd:complexType name="annotation">
<xsd:sequence>
<xsd:element name="annotationName" type="EQName"/>
<xsd:element name="arguments" type="literalList" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
and:
<xsd:complexType name="literalList">
<xsd:sequence>
<xsd:element ref="constantExpr" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
Thanks for observing this problem!
I've marked this bug as RESOLVED/FIXED. If you agree, please mark it CLOSED.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Sunday, 17 March 2013 22:43:17 UTC