Lists Home |
Date Index |
Thanks Arthur. I should explain why I asked the
question because being an XML-Dev regular and
a markup veteran, I do have some experience with
schemas, DTDs, etc.. In SGML, schemas were the
beginning of the discussion, not a sidebar. In
XML they are often Chapter Zed and are described
in deprecative language. That leaves an impression
among recent converts to XML that they are to be
avoided or are just a form of documentation.
I was recently handed a self-paced tutorial on .Net
and told to run it so that I could understand 'the
Microsoft point of view on XML and web services' to
make my discussions with developers less abstract and
more production-oriented. ;-) The answer Dare gave
to my question ensured
that it was understood that schemas are not irrelevant
to .Net. I realize the system library has a validator,
but the presentation of the course material doesn't
make much of these capabilities and leaves the impression
among local implementors and their managers that
XML Schemas can be safely ignored. Such an impression
exacts a price later when it is expensive to pay.
From: Arthur Colman [mailto:firstname.lastname@example.org]
.Net's use of schema is very convenient. There are limits to Visual
Studio's ability to easily take a schema and convert it into a dataset.
However, I would state that these limitations are more due to me taking
document oriented schema and attempting to convert it into a database
So, instead of being able to convert an XML message directly into a data
store one has to do some translation. I don't think this is so much a
limitation of .Net but some growing pains associated with the tools.