Re: Namespaces, schemas, Simon's filters.

[Peter Piatko <piatko@research.telcordia.com>]

Locals names might be interpreted as belonging to the namespace of the
complexType they are associated with, if that's what you mean.  In XML
Schema, I believe that one may import types from other namespaces, so the
local element may in fact not be associated in any way with the namespace of
the ancestor "global" element in an instance document.  (If my understanding
of this is correct).

Thanks,

Peter

----- Original Message -----
From: "Jeff Lowery" <jlowery@scenicsoft.com>
To: <xml-dev@lists.xml.org>
Sent: Wednesday, August 29, 2001 6:54 PM
Subject: RE: Namespaces, schemas, Simon's filters.


> > I see nothing wrong with a rule that says if you're going to
> > give something
> > a name, give a unique name. There's not way to enforce that,
> > of course, but
> > we're dealing with it for namespace identifiers already.
>
> Er, should have said "disambiguatable name", not "unique name". This would
> include non-unique local names that are disambiguated by the context of
> being in a parent element, and so on up the chain, until an ancestor
element
> is found that is global w.r.t. a namespace.
>
> Thus local names are associated with a namespace (and I'll take any
> definition of "associated" you care to give), and any context that the
> namespace might connote would be inferrable.
>
> Again, I would like to know why it was decided that namespaces be
> represented as attributes rather than parent elements, since it seems
> elements (superficially at least) are a more natural representation.
> Understanding breeds contentment, right?
>
>
> -----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
>
> The list archives are at http://lists.xml.org/archives/xml-dev/
>
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.xml.org/ob/adm.pl>
>
>