Re: Issue 13.3.1: the 'create' operator

[Andy Bierman <abierman@cisco.com>]

At 10:44 AM 2/21/2004, Phil Shafer wrote:
>Andy Bierman writes:
>>I don't see why this should be optional.
>>I understand why #candidate, #writable-running, and
>>even #rollback need to be capabilities, but not this.
>
>I said "optional", not "capability".  Optional in that it shouldn't
>be _required_ to create a node.  Is that what the argument is over?

I guess so. I misunderstood you.
I agree that merge, replace, and delete should
work exactly as currently defined, and the default value
is merge.

Andy



>My comment was that as an optional attribute, fine, but not a
>mandatory one.  If I have a chunk of xml to add, I shouldn't have
>to transform it to add a useless attribute when I want to add the
>entire chunk.
>
>    <foo>
>      <goo/>
>    </foo>
>
>should always make foo and goo.
>
>   <foo create="create">
>     <goo/>
>   </foo>
>
>should create foo (and goo) if and only if foo does not
>exist.
>
>Thanks,
> Phil
>
>--
>to unsubscribe send a message to netconf-request@ops.ietf.org with
>the word 'unsubscribe' in a single line as the message text body.
>archive: <http://ops.ietf.org/lists/netconf/> 


--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>