Andy Bierman wrote:
Phil Shafer wrote:
Final clarification on this issue: If a particular filter node does not use any namespace, then it must match a corresponding node in the data model which also does not use any namespace. Use of the default namespace does not act as a wildcard to ask the agent to find the correct namespace. Andy
Andy Bierman writes:Your example obviously shows it doesn't matter where the xmlns directives are in the PDU. All that matters is normal XML processing rules are followed to determine the requested namepsace.Yup, the text is an encoding of the infoset, and there are multiple ways to encode it.This does not work. Although extremely stupid, empty strings and whitespace-only strings are valid namespace names. (I wonder how many agents handle an empty NS string correctly?)You sure? In section 5.2 of: http://www.w3.org/TR/1999/REC-xml-names-19990114/ it says: The default namespace can be set to the empty string. This has the same effect, within the scope of the declaration, of there being no default namespace. There's an example also.Okay, you are right. The libxml2 parser behaves this way: <foo/> no namespace <t:foo xmlns:t=""/> namespace = "" <foo xmlns=""/> no namespace One more weird XML corner case to deal with :-( Is this supposed to be a feature?Thanks, PhilAndy -- 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/>