1462 2005-05-17 18:28:07 +0000 sequenceExpr use in XQueryX 2005-09-29 09:05:07 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XQueryX 1.0 Last Call drafts PC All CLOSED FIXED P2 normal --- 1 bshrom jim.melton public-qt-comments oldest_to_newest 3166 0 bshrom 2005-05-17 18:28:07 +0000 Hello, What would be a correct XQueryX statement for the following XQuery: ("FOO", "BAR") According to the XQueryX schema this is valid statement: <xqx:module xmlns:xqx="http://www.w3.org/2005/04/XQueryX" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.w3.org/2005/04/XQueryX ../xsd/xqueryx.xsd"> <xqx:mainModule> <xqx:queryBody> <xqx:expr xsi:type="xqx:pathExpr"> <xqx:argExpr> <xqx:expr xsi:type="xqx:sequenceExpr"> <xqx:expr xsi:type="xqx:stringConstantExpr"> <xqx:value>FOO</xqx:value> </xqx:expr> <xqx:expr xsi:type="xqx:stringConstantExpr"> <xqx:value>BAR</xqx:value> </xqx:expr> </xqx:expr> </xqx:argExpr> </xqx:expr> </xqx:queryBody> </xqx:mainModule> </xqx:module> However, if you run XQueryX->XQuery stylesheet transformation it will produce: (FOO)(BAR). In the recent release of the stylesheet new for-each cycle have been added to the template for sequenceExpr, that breakes the conversion. <xsl:template match="xqx:expr[@xsi:type='xqx:sequenceExpr']"> <xsl:for-each select="*"> <!-- NEW --> <xsl:call-template name="paranthesizedList"> <xsl:with-param name="delimiter" select="$COMMA_NEWLINE"/> </xsl:call-template> </xsl:for-each> <!-- NEW --> </xsl:template> Is it a bug or I'm missing something here, below I provided AST for ("FOO","BAR") in the XML form: <XPath2> <QueryList> <Module> <MainModule> <Prolog/> <QueryBody> <Expr> <PathExpr> <ParenthesizedExpr> <Expr> <PathExpr> <StringLiteral>"FOO"</StringLiteral> </PathExpr> <PathExpr> <StringLiteral>"BAR"</StringLiteral> </PathExpr> </Expr> </ParenthesizedExpr> </PathExpr> </Expr> </QueryBody> </MainModule> </Module> </QueryList> </XPath2> 4359 1 jim.melton 2005-06-27 01:22:33 +0000 Many thanks for your comment and rather detailed research. You identified a newly-introduced bug in the stylesheet, which has been corrected. When a new version of the XQueryX spec has been published, we hope that you will review it and, if it resolves this issue, you will mark the issue CLOSED. Jim Melton On behalf of the XML Query Working Group 6573 2 jim.melton 2005-09-29 09:05:07 +0000 Since the commenter has not objected to the solution published in the XQueryX draft published on 2005-09-15 (two weeks ago today), I am marking this bug CLOSED. If this is not satisfactory, the commenter may re-open the bug and explain his reasons.