OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: [xml-dev] nested namespaces

[ Lists Home | Date Index | Thread Index ]

Simon St.Laurent wrote:

> More generally, I'm wondering about cases where developers use container
> elements in one namespace which may be different from either the
> namespace of the parent element or the namespaces used by the child
> elements.
> For example:
> <a:container 
>      xmlns:a="http://example.com/a";
>      xmlns:b="http://example.com/b";
>    >
>    <b:container>
>      <a:leaf />
>      <a:branch>
>        <a:leaf />
>      </a:branch>
>      <a:leaf />
>    </b:container>
> </a:container>
> Some people seem to assume that elements in namespaces you don't
> understand can be discarded, but what gets discarded here?  

That's a difficult assumption to hold. Namespaces are purely for 
partitioning names - pedantically, that's not the same as a 
processing model for names. Thinking about it, discarding what you 
don't know is effectively a bug *unless* you've defined a protocol 
or a policy over and above namespaces for handling unknown sets of 
names. I haven't got to Marks' draft yet, but it seems like you're 
wanting to treat namespaces as a form of processing instruction or 
dispatch mechanism.

> Any thoughts?  I don't see any obvious answers here.

I doubt there are any. When you get down to it there's not much 
difference between unrecognized input and garbage input - other than 
perhaps it meant something to the origin producer.

Bill de hÓra


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS