Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xml-dev] XML spec and XSD

From: Mukul Gandhi <gandhi.mukul@-----.--->
To: Jim Melton <jim.melton@---.--->
Date: 11/8/2009 4:24:00 AM
Thanks, Jim for some nice comments.

My intention was not to say, that DTD is now not useful. As you
rightly said, DTD is still preferred over XSD for certain class of
problems.

My averment was to give XSD the same status as DTD, as a XML
validation technology in W3C XML spec.

On Sun, Nov 8, 2009 at 1:31 AM, Jim Melton <jim.melton@a...> wrote:
> I'm one of those people who don't fall in love with technologies for their
> own sake, regardless of how beautiful and/or useful they might be.  I do
> have a fondness for elegance, as well as for practicality, but I believe
> that technology provides tools and nothing more.  XSD is one such tool, DTD
> is another.  Each has its uses, and I use them both.
>
> As Simon has pointed out, DTDs do a great job for document-centric
> applications where there is little that needs to be known about the
> semantics of atomic data types.  I use DTDs for my editing work on the SQL
> standard and on W3C documents, as well as for a host of other documents I do
> in other aspects of my day job and my life.
>
> Schemas are often very clumsy for validating "ustructured" textual
> documents, such as fiction books, biographies, and the like.  But schemas
> (XSD being the W3C-defined instance of this technology) are very useful when
> dealing with structured documents, especially those that contain lots of
> traditional data and/or those that are generated specifically from data (not
> to mention those that *are* data expressed in an XML tree).
>
> I get very, very frustrated when I'm trying to drive a nail into their wall
> using a screwdriver, as well as when I'm trying to get a screw out of the
> wall using a hammer.  That doesn't make me hate the screwdriver or the
> hammer -- nor, for that matter, to love either one when I figure out that I
> got it backwards and start using the proper tool for each job.  They're just
> tools.  Pick the right one for your job.
>
> If your management is forcing you to use XSD for unstructured document
> validation (or DTDs for highly structured data validation), don't hate XSD
> (or DTD)...hate the bureaucracy that limits your choice of tool!
>
> Hope this helps,
>   Jim
>
> ========================================================================
> Jim Melton --- Editor of ISO/IEC 9075-* (SQL)     Phone: +1.801.942.0144
>  Chair, W3C XML Query WG; XQX (etc.) editor       Fax : +1.801.942.3345
> Oracle Corporation        Oracle Email: jim dot melton at oracle dot com
> 1930 Viscounti Drive      Standards email: jim dot melton at acm dot org
> Sandy, UT 84093-1063 USA          Personal email: jim at melton dot name
> ========================================================================



-- 
Regards,
Mukul Gandhi

_______________________________________________________________________

XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.

[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@l...
subscribe: xml-dev-subscribe@l...
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php



transparent
Print
Mail
Like It
Disclaimer
.

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 www.altova.com/list/index.html. 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.

.
.

transparent

transparent