26757 2014-09-08 16:10:02 +0000 [UPD30] XQueryX for Update 3.0 2014-11-06 23:37:17 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Update 3.0 Working drafts All All RESOLVED FIXED P2 normal --- 1 jmdyck jim.melton jim.melton public-qt-comments oldest_to_newest 111172 0 jmdyck 2014-09-08 16:10:02 +0000 Appendix E "XML Syntax (XQueryX) for XQuery Update Facility 3.0" appears to be unchanged from 1.0 (other than changing version numbers). Presumably the schema and stylesheet need additions for constructs that are new in 3.0: UpdatingFunctionCall and (soon) ModifyExpr (bug 23643). 114623 1 jim.melton 2014-11-06 23:37:17 +0000 Michael, thanks for this report. You are correct that the XQueryX schema and stylesheet require modification for UpdatingFunctionCall. I will make those changes immediately. The changes related to bug 23643 are not as simple. According to https://www.w3.org/Bugs/Public/show_bug.cgi?id=23643#c21, the solution to that bug is: Rename the current TransformExpr to CopyModifyExpr, and name the nonterminal for the "transform with" expression TransformWithExpr. Of course, I can easily create a new element for the TransformWithExpr, which I'll do immediately. However, for backwards compatibility with Update 1.0, I cannot rename the XQueryX element corresponding to TransformExpr to another name. I could modify the location where TransformExpr is used so that there is an alternative named CopyModifyExpr, then create a new element CopyModifyExpr that (other than its name) is identical to the current TransformExpr, but that seems like a lot of make-work. For example, the following addition would basically accomplish what I described in the immediately preceding paragraph: <xsd:element name="copyModifyExpr" type="xqxuf:transformExpr" substitutionGroup="xqxuf:expr"/> That would be accompanied by the following change to the stylesheet: <xsl:template match="xqxuf:transformExpr | xqxuf:copyModifyExpr"> But the existing element named transformExpr would have to remain for backwards compatibility. Under the not-too-unreasonable assumption that this is the best approach, I have done all of the above and marked the bug RESOLVED/FIXED. If you are satisfied with these changes, please mark it CLOSED. You can find the changes in the internal draft of XQuery Update 3.0 in CVS space.