Issue 11 - It's Baaaack

[Danny van der Rijn <dannyv@tibco.com>]

during today's conference call, we took a straw poll, where approximately
2/3 voted to attempt to resolve issue 11.  (i'll leave the exact count to
the minutes).  i would like to resurrect a large part of my previous
proposal (i'll drop "rename").  to me, this is a viable proposal, and i
would be satisifed if it ended up being adopted into the spec.  however,
maybe in the months since we last thought about it, someone else has a
reasonable alternative.

danny

My proposal:  under the <assign> element, there will be 6 possible
elements, where now there is only 1.

<copy>
  <from/>
  <to/>
</copy>
as current.
-----------------------------
<insertBefore>
  <from/>
  <to select="XPath Expression evaluates to one node"/>
</insertBefore>

creates a sibling before the select expression
-----------------------------
<insertAfter>
  <from/>
  <to select="XPath Expression evaluates to one node"/>
</insertAfter>

creates a sibling after the select expression
-----------------------------
<append>
  <from/>
  <to select="XPath Expression evaluates to one node"
        child="integer XPath expression"? />
<append>

creates a child of select expression at the child-th position.  child
defaults to last().
-----------------------------
<remove select="XPath expression evaluates to one node">

removes a node