[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: Why Doesn't IE5 use the DTD to Validate?

Subject: RE: Why Doesn't IE5 use the DTD to Validate?
From: "Didier PH Martin" <martind@xxxxxxxxxxxxx>
Date: Wed, 31 Mar 1999 20:53:40 -0500
validation of overkill
Hi Daniel,

<YourComment>
	While I see your point in terms of validation, I think that
Jonathan's argument is sound.
As a content provider, I can see little need for *client-side* validation,
except in certain special cases. Validation against a DTD is a check for
structural validity, and should be carried out by the author prior to
serving the document. As Jonathan notes, what is the client supposed to do
on receiving an invalid document? Popping up a Javascript alert box is not
acceptable, nor is refusing to show the page. We must work on the assumption
that the author validated the document. Also, validation by clients would
simply take too long and be too large a performance hit. Validation is for
author's to check their work, not for browsers to check their input. (These
arguments do not apply to well-formedness.)
</YourComment>

<Reply>
I cannot agree more. In fact, if we take a neutral perspective. Even Mozilla
will take the same path. We learned from the last years on the net that
browsers have to be able to minimize a) publication requirement (the least
is the best) b) to resist to different "near perfect" documents. There is no
real needs to do validation except to increase the end user frustration.
However, probably this will needed in business to business transactions or
e-commerce. In that case, the goal is not rendition but information
exchange. Because the system that receives the information need valid data.
There is a need for more structured exchange and therefore for validating
parsing. So:

a) for rendition in browsers validation is overkill and not really
necessary. We have to reduce publication frictions
b) for information exchange like business to business transactions (i.e.
EDI) validation becomes necessary to prevent the "garbage in" problem to ERP
systems.

Thus, these two distinct XML usages requires different way to process (i.e.
parse) the documents. Its simply a matter of choosing the right stuff for
the right occasion :-)
</Reply>

Regards


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


Current Thread

PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.