[netmod] nested insert operations (yang-08, 7.7.7 and 7.8.6)

[Andy Bierman <andy at netconfcentral.com>]

Hi,

I am not sure the text in these sections wrt/
nested nc:operation attributes is very clear,
or nested insert operations are explained at all.

The higher level operation (closer to root) has precedence
over the nested operation.  There are lots of implementation
details omitted, but essentially, a 'replace' operation
takes affect the first descendant-or-self node that actually changed.
So any insert operations nested within the 'replace' operation
do not have any existing list or leaf-list, as explained in
the draft:

7.7.7, para 6:
   In a <copy-config>, or an <edit-config> with a "replace" operation
   which covers the entire leaf-list, the leaf-list order is the same as
   the order of the XML elements in the request.

An insert nested within a nc:operation=replace is really ignored,
and should probably be flagged as an error. (The request PDU order
is used instead.)

=================================

7.7.7, para 4:
   If no "insert" attribute is present in the "create" operation, it
   defaults to "last".

Doesn't this default apply to 'merge' as well?

Isn't the order required (key or value attributes)
if the operation is 'replace'?  Or is it just a NO-OP,
and the server leaves the list or leaf-list in the same place?


Andy