20864 2013-02-04 14:30:44 +0000 [XQX30] Annotation arguments 2013-11-19 00:16:48 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XQueryX 3.0 Candidate Recommendation PC Windows NT CLOSED FIXED P2 normal --- 1 tim jim.melton public-qt-comments oldest_to_newest 82525 0 tim 2013-02-04 14:30:44 +0000 XQueryX annotations allows expressions as arguments, rather than restricting the arguments to be literals. <xsd:complexType name="annotation"> <xsd:sequence> <xsd:element name="annotationName" type="EQName"/> <xsd:element name="arguments" type="exprList" minOccurs="0"/> </xsd:sequence> </xsd:complexType> 84536 1 jim.melton 2013-03-17 22:43:16 +0000 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. 87343 2 tim 2013-05-07 16:16:08 +0000 Thanks. I'm happy that this resolves the problem. 96483 3 jim.melton 2013-11-19 00:16:48 +0000 The author of the original bug report agrees that it has been resolved to his satisfaction. The fact that it was not marked CLOSED at the time was accidental, so I am marking it CLOSED now.