OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   RE: [xml-dev] Interesting mailing list & a rare broadside

[ Lists Home | Date Index | Thread Index ]

Title: RE: [xml-dev] Interesting mailing list & a rare broadside

This rather nicely demonstrates the need for multiple schema languages.

If XML Schema had the ability to specify allowed root nodes, it would become even more complex (you'd need to also be able to specify root *types* as well, I think, & perhaps that a given element may only be the root if it has a particular attribute & <xsd:any namespace="http://www.w3c.org/2002/hideouslyComplexSchemaRules" /> ).

If RELAX provided some inheritance support (putting aside arguments as to whether a schema language should or not), it would start to become more complex.

If either of these languages provided support for complex co-constraints, things would get out of hand.

Schematron allows you to define allowed roots for a schema, and I dare say it won't be long before someone devises a streaming Schematron processor, so by combining the required features of different schema languages, all kinds of things are possible. It's also IMHO a much neater way to specify things like key/keyref relationships.

I think they called it component based development in the 90's. XSD doesn't have to be complex, regarless of verbosity, so perhaps the answer is to try to refactor it as a set of modular features, which you can specify as being supported or not in a schema or a processor (I'd personally always turn off complex type restriction).

I don't believe XSD is inherently evil (except with a hangover on a Monday morning), any more than the Dutch tax laws are (which are also hideously complicated and subject to multiple interpretations, though some would argue that *all* tax laws are evil) and it has some useful stuff. It would be nice to see XSD V2.0 heading towards simplification - maybe even <heresy>interoperable with RELAX NG</heresy> where each of the languages focuses on it's core competency as a component in a possible whole. However, having never designed a schema language, I have no idea if this is either possible or desirable.


-----Original Message-----
From: Bullard, Claude L (Len) [mailto:clbullar@ingr.com]
Sent: 05 June 2002 21:55
To: 'Elena Litani'; Simon St.Laurent
Cc: xml-dev@lists.xml.org
Subject: RE: [xml-dev] Interesting mailing list & a rare broadside

Wouldn't it have been better to provide something
analogous to DOCTYPE support where

<!DOCTYPE thisIsTheROOTforThisPass

is explicit rathen than relying on syntactic
position which may be accidental?


From: Elena Litani [mailto:elitani@ca.ibm.com]

Xerces doesn't provide a way to specify a validation root, thus the
assumption is that the first element encountered by the
XMLSchemaValidator is the validation root.  

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 list use the subscription
manager: <http://lists.xml.org/ob/adm.pl>

The information transmitted by this e-mail message is intended solely for the use of the person to whom or entity to which it is addressed. The message may contain information that is privileged and confidential.  Disclosure, dissemination, distribution, review, retransmission to, other use of or taking any action in reliance upon this information by anyone other than the intended recipient is prohibited. If you are not the intended recipient, please do not disseminate, distribute or copy this communication, by e-mail or otherwise. Instead, please notify us immediately by return e-mail (including the original message with your reply) and then delete and discard all copies of the message.

Although we have taken precautions to minimize the risk of transmitting viruses we nevertheless advise you to carry out your own virus checks on any attachment to this message. We accept no liability for any loss or damage caused by viruses.


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS