Altova Mailing List Archives

Re: Namespaces, schemas, Simon's filters.

From: Evan Lenz <elenz@-------.--->
To: Peter Piatko <piatko@--------.---------.--->,Ronald Bourret <rpbourret@---------.--->, xml-dev@-----.---.---
Date: 8/25/2001 10:47:00 AM
Peter Piatko wrote:
> "...In this example, there are three occurrences of the name title within
> markup, and the name alone clearly provides insufficient information to
> allow correct processing by a software module."
> The implication of this sentence is that the type and the identifier
> have a 1-1 mapping.

I think that section is non-normative for a reason. I imagine that it's
mainly to help justify the reasoning behind why attributes do not inherit
the default namespace. This implies a set of conventions, but it does not
mandate those conventions. I think the Namespaces syntax is sufficient as is
(many think it's far too sugary, let alone not sugary enough).

> (b) simplify (i.e.
> flatten) the interpretation of what namespaces are.

I've always had this "flattened" interpretation of Namespaces. This is
reflected in the design of my de facto schemas...

> Option (b) implies that an identifier might map to multiple types.  I
> the question boils down whether this ok or not. I hope it's okay!

Evan Lenz
XYZFind Corp.


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.