As with UML, I think discerning between
the redundant and obscure features is hard, but using the
basic parts of the spec is easy.

I thought DTDs were hard too.  Just about
anything new is hard I guess.  It depends
on how motivated you are.

Many developers are comparing Schemas
to DTDs and wondering if it's worth it.  It
depends on the project.  Projects
that cross company boundaries should use
Schemas because namespaces should be used
and Schemas will be more "standard" than the
other schema languages.  That's assuming Simon
isn't working at Oracle, IBM, Sun, and Microsoft 
simultaneously.  :)

Others may disagree as usual.

----- Original Message -----
From: "Bullard, Claude L (Len)" <clbullar@[...].com> 
To: "Michael Brennan" <Michael_Brennan@[...].com> ; "'Nicolas LEHUEN'"
<nicolas.lehuen@[...].com> 
Cc: "'xml-dev'" <xml-dev@[...].org> 
Sent: Wednesday, August 22, 2001 1:44 PM
Subject: Why Are Schemas Hard? (WAS RE: "Uh, what do I need this for" (was
RE: XML.COM: How I Learne d t o Love daBomb))


1.  What about Schemas is hard?







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