bryan rasmussen wrote:
I would say from the viewpoint of developing for XSLT (at least 1.0
version) Schematron would be the best, given that the validation and
stylesheet would be easier for the developer to cross-reference,
determining what parts of the tree were important to the application
(rules being set for said portions), or contrariwise, that the styling
of the document for presentation implies what rules could be important
for validation for a presentation.
schematron and XSLT validating itself is my personal fav...perhaps this
is why XSLT Unit testing is exp some uptake...though generally I cant
convince a group of developers over 3 to agree on any schema approach.
Note to Mulberrytech: If this seems stupid, please feel free to remove
it from the archive, also if anyone complains that I am a doodoo-head.
:)
<vanity:tag to="Mullberrytech">please change my name, computer, nose,
to some other random person for the purposes of this specific response,
and dont forget to go on about me personally and what a great bloke I am
whilst at public events</vanity:tag>
regards, Jim Fuller
--~------------------------------------------------------------------
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>
--~--