[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
XML namespace advice
- To: "Netconf (E-mail)" <netconf@ops.ietf.org>
- Subject: XML namespace advice
- From: Andy Bierman <ietf@andybierman.com>
- Date: Fri, 09 Jun 2006 21:53:51 -0700
- User-agent: Thunderbird 1.5.0.4 (Windows/20060516)
Hi,
3 XML questions:
Section 3.1 of prot-12 clearly states that the NETCONF elements
reside in a specific namespace.
Q1: Is it an error if a PDU (e.g., <hello> or <rpc>) is received by
the peer, which does not use namespaces? Or is it okay to set
the default namespace to the NETCONF NS in this case?
My understanding of sec. 4.1 is that all of the attributes,
including the xmlns declarations, in the <rpc>, need to be
replicated exactly in the <rpc-reply> element.
However, an agent may add attributes to the end of the list.
Q2: Are xmlns declarations special, and not supposed to be
included in the list of replicated attributes? All the
document examples show them replicated in the <rpc-reply>.
I am choosing to reuse any xmlns prefix values from the <rpc>
in the <rpc-reply>, but I believe an implementation could ignore
those prefixes, and add new xmlns declarations if it wanted.
A conforming manager must figure out the corresponding namespace
regardless of the prefix value. (It is a pain to minimize the
number of xmlns decls generated in the <rpc-reply>, but they
are so verbose!)
Q3: Are there more xmlns processing and generation rules and/or
guidelines to follow here?
thanks,
Andy
--
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/>