- From: <bugzilla@wiggum.w3.org>
- Date: Fri, 23 Jun 2006 08:40:59 +0000
- To: public-qt-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=3333 ------- Comment #4 from jim.melton@acm.org 2006-06-23 08:40 ------- Obviously, the minimal fix is a modification to the stylesheet's template that processes the <xqx:flworExpr/> element -- that fix, of course, is to insert an <xsl:value-of select="$LPAREN"/> element preceding the template's <xsl:apply-templates/> instrucction, and an <xsl:value-of select="$RPAREN"/> after. I am making that change regardless. A second change, suggested by http://www.w3.org/Bugs/Public/show_bug.cgi?id=3333#c2, would remove the <xqx:parenthesizedExpr/> element entirely. I am slightly reluctant to do so, in spite of the comment in http://www.w3.org/Bugs/Public/show_bug.cgi?id=3333#c3 that it serves no "useful purpose for XQueryX to retain knowledge of where the parentheses appear...". There is no intent of "retaining knowledge", which implies that such knowledge exists; XQueryX is not intended to be produced as a transformation from an XQuery. The question is whether the author of an XQueryX document wishes to explicitly parenthesize an expression. In spite of my reluctance, I yield to my reviewers and have removed the <xqx:parenthesizedExpr/> element.
Received on Friday, 23 June 2006 08:41:03 UTC