Re: netconf XML namespace

[Rob Enns <rpe@juniper.net>]

Thanks Tom, I'll make the proposed change in the next version
of the netconf draft.

Rob

On Thu, Feb 05, 2004 at 04:13:12PM -0000, Tom Petch wrote:
> Section 8.3, No Attributes in the Default Namespace, seems to contradict
> RFC 3470.
> 
> The RFC says
> 
> 4.9.1 Namespaces and Attributes
> 
>    There is a frequently misunderstood aspect of the relationship
>    between unprefixed attributes and the default XML namespace - the
>    natural assumption is that an unprefixed attribute is qualified by
>    the default namespace, but this is not true.  Rather, the unprefixed
>    attribute belongs to no namespace at all.
> 
> 
> whereas 8.3 says
> 
>    Do not use attributes in the default namespace.  All attributes
>    should be qualified.
> 
>    Unqualified attributes belong to the default namespace, and their use
>    pollutes the default namespace.  Restricting them to the current
>    namespace encourages meaningful definitions that are free of
>    collisions.
> 
> But I would also like 8.3 to stress the positive rather than the negative,
> eg
> 
> 8.3 Namespaces
> 
> All attributes should be prefixed so that they belong to a specific
> namespace. This
> encourages meaningful definitions that are free of collisions.
> 
>      <valid xmlns="http://valid/"; xmlns:v="http://valid/";
> v:foo="cool"></valid>
> 
>      <not-valid xmlns="http://not-valid/"; foo="not-cool"></not-valid>
> 
> 
> Tom Petch
> 
> 
> --
> 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/>