Hi,
At 04:59 PM 5/20/2010, you wrote:
Hi Folks,
My thinking is that the input data should be checked using XML
Schema and Schematron. Ditto for the data that is output by XSLT.
I see no reason to include in an XSLT program any code to check
data. It just makes the program bigger, harder to understand, harder
to maintain, and harder to debug.
Do you agree?
I agree with both observations:
(a) XSD (or your schema language of choice) plus Schematron are very
good at checking data.
(b) Doing the same thing in your XSLT can be costly, unwieldy, and
difficult to maintain.
But I don't think it follows follows from either or both of these
that doing so is, categorically, a bad idea.
I'm afraid this is like saying there's never any point in a car with
a hatchback, since you can always haul things in your pickup truck.
It may be largely true, and it may be especially true for you, but
that doesn't mean it's always true for everyone.
Cheers,
Wendell
======================================================================
Wendell Piez
mailto:wapiez(_at_)mulberrytech(_dot_)com
Mulberry Technologies, Inc. http://www.mulberrytech.com
17 West Jefferson Street Direct Phone: 301/315-9635
Suite 207 Phone: 301/315-9631
Rockville, MD 20850 Fax: 301/315-8285
----------------------------------------------------------------------
Mulberry Technologies: A Consultancy Specializing in SGML and XML
======================================================================
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--