[Bug 26757] [UPD30] XQueryX for Update 3.0

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26757

Jim Melton <jim.melton@acm.org> changed:

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

--- Comment #1 from Jim Melton <jim.melton@acm.org> ---
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.

Received on Thursday, 6 November 2014 23:37:18 UTC