Cart
[Home] [By Thread] [By Date] [Recent Entries]
Dear George,
If a stylesheet isn't valid on its own when the user initiates validation, perhaps the user could be prompted to nominate another stylesheet (i.e. the main one) to validate in its place. Perhaps this setting could be "sticky" in a session. That is, I'm in favor of option 1, except I'd like the default behavior to be to validate this stylesheet, with the option of validating another one offered only if there's trouble. As far as the difficulty of having many of these to set when an import tree is complex, perhaps this is the point when heuristics could be applied to a project, and a likely candidate or candidates for "main stylesheet" nominated in a pick-list. That would alleviate some of the burden, while allowing developers to retain control. I've sometimes had modules that had more than one calling stylesheet, after all (it's part of the point of a modular design), so I'd rather not leave this completely up to the machine to decide. Cheers, Wendell At 08:20 AM 2/2/2006, you wrote: When you perform a stylesheet validation in oXygen it tries to create a Transformer out of that using the XSLT processor you have configured for XSLT validation. By default that is Saxon 6.5.5 for XSLT 1.0 and SaxonB 8.6.1 for XSLT 2.0. ====================================================================== Wendell Piez mailto:wapiez@xxxxxxxxxxxxxxxx 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 ======================================================================
|
