Re: XML Namespace usage in NETCONF

[Phil Shafer <phil@juniper.net>]

Andy Bierman writes:
>The problem is that the <rpc> and <get> parent elements
>are defined in a target namespace, so namespaces are being used.

Sure, since you haven't changed the namespace.  You can encode
this to but <top> in the default namespace as follows:

<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
  <get>
    <filter type="subtree">
      <top xmlns=""/>
    </filter>
  </get>
</rpc>

or:

<nc:rpc message-id="101" xmlns:nc="urn:very:long">
  <nc:get>
    <nc:filter type="subtree">
      <top/>
    </nc:filter>
  </nc:get>
</nc:rpc>

These are different encoding for the same infoset.

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/>