[Bug 26757] New: [UPD30] XQueryX for Update 3.0

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[Bug 26757] New: [UPD30] XQueryX for Update 3.0

Bugzilla from bugzilla@jessica.w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26757

            Bug ID: 26757
           Summary: [UPD30] XQueryX for Update 3.0
           Product: XPath / XQuery / XSLT
           Version: Working drafts
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Update 3.0
          Assignee: [hidden email]
          Reporter: [hidden email]
        QA Contact: [hidden email]

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).

--
You are receiving this mail because:
You are the QA Contact for the bug.

Reply | Threaded
Open this post in threaded view
|

[Bug 26757] [UPD30] XQueryX for Update 3.0

Bugzilla from bugzilla@jessica.w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26757

Jim Melton <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #1 from Jim Melton <[hidden email]> ---
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.

--
You are receiving this mail because:
You are the QA Contact for the bug.