Altova Mailing List Archives

Re: [xml-dev] Finally, what if namespaces == document types ?

From: "Simon St.Laurent" <simonstl@--------.--->
To: Paul Prescod <paul@-------.--->
Date: 1/23/2002 10:57:00 PM
On Wed, 2002-01-23 at 17:29, Paul Prescod wrote:
> Here's my model for thinking about namespaces. You figure out the
> "controlling" namespace. Usually this is the one on the root element but
> not always. You hand the document to a processor that knows how to
> handle that data. It does some arbitrary rewriting of the data that
> conforms to another namespace. THEN, it OPTIONALLY hands the rewritten
> data to a processor that knows only about the inner namespace...and so
> forth recursively.

And if the controlling namespace is no namespace at all?

My rules files for namespace and regular fragmentation processing are
very content to live inside any root element.  They don't particularly
care about control.

Rewriting the data sounds like you're trying to force square pegs into
elliptical holes.  Maybe that's appropriate sometimes, but I can't see
it as a general case.
Simon St.Laurent
Ring around the content, a pocket full of brackets
Errors, errors, all fall down!


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.