Altova Mailing List Archives

RE: [xml-dev] Strategies for a lowly XML document

From: Michael Brennan <Michael_Brennan@-------.--->
To: "'Bill Lindsey'" <bill@-----.--->, xml-dev@-----.---.---
Date: 1/23/2002 10:28:00 PM
> From: Bill Lindsey [mailto:bill@b...]


> I'd be particularly interested in hearing
> arguments that this approach:
>  * somehow subverts W3C Schemas or Namespaces
>   * requires W3C schema validation or PSVI processing
>  * interferes with W3C schema validation or PSVI processing
>   * favors any particular schema language over others
>  * is ugly

How about this now bases a generalized processing model on XML Schema's
notion of types -- something that has proven to be quite controversial, and
has *not* proven itself to be a generalized-enough foundation for very
general XML architectures. In fact, it has been proven that XML Schema types
cannot adequately model all possible XML structures, so you've just
constrained this approach to be restricted to only a subset of possible

DOCTYPEs have their own problems, but they are already there in the
foundation of XML, so we have to contend with them.

I have a big problem with basing this on XML Schema types.


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.