Hi, I second Lars' request for generally tighter validation of Schematron, especially when it comes to XPaths. This would really help tighten the development cycle. It could be that converting the Schematron into XSLT for validation isn't necessary, if the editor could be aware of Schematron in a way similar to its awareness of XSLT ... in particular, that Schematron rule/@context and (assert|report)/@test attributes need to be XPath. I suppose this is complicated by the fact that they don't ... a Schematron might have any of a number of queryBinding values at the top level. But presumably it makes sense for oXygen to validate only the query languages it actually supports. Could oXygen be smart enought to check for XSLT 1.0 XPath when queryBinding="xslt" and XSLT 2.0 XPath when queryBinding="xslt2"? To be really complete, it would also have to traverse Schematron include elements and even xsl:import or xsl:include elements (for those of us who mix XSLT in, and maintain XSLT functions in other modules). Cheers, Wendell ====================================================================== Wendell Piez mailto:wapiez@mulberrytech.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 ======================================================================