At 05:31 AM 4/28/2005, you wrote:
It also increases the chances that the stylesheet will do something
unwanted when the schema changes
Unless your definition of "unwanted" considers that data being silently
dropped is more unwanted than data passed through even to an invalid result....
(Not that there aren't third possibilities like trapping an exception in
some way for unexpected input, for example by using xsl:message or any of a
number of other techniques. But the point is, sometimes you'll be
expressing and controlling tighter constraints over your output than over
your input -- if you are validating your output you can rely on that to
catch problems there; but validation processes can't usually see where data
that was there, is now missing. So what's "unwanted" depends on the
context. Or to put it another way, you're right -- and sometimes it's a
good thing that your stylesheet does something unwanted.)
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>
--~--