Altova Mailing List Archives

Re: [xml-dev] Re: [dsdl-comment] Re: [xml-dev] Re: Re: [xml-dev] DSDL: use cases: namespace declaration notation

From: james anderson <james.anderson@----.-->
To: xml-dev@-----.---.---
Date: 6/14/2002 4:45:00 PM
David Carlisle wrote:
> >  I note that the recommendation specifies a notion which is untenable.
> > ...
> > I do take issue with claims that this set does not exist.
> I suspect that the reason for not calling it a namespace is that you are
> supposed to think of it as multiple sets which are not distinguished in
> the syntax.

This conflates the behaviour of sets of names with that of the mechanisms which bind names to other things, like element and
attribute declarations.

> That is, if you have two documents that contain the element
> {}math then they are references to the
> same element in the same set (the mathml namespace)
> However if you have two documents referencing {}math then arguably they
> are not intended to be the same element, It may be that they are in
> different sets of elements but that the XML namespace syntax does not
> distinguish that (maybe the application does using other info, eg the doctype).



These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.