Hey George et al., I just posted on the web forum a question about getting SVRL out of a Schematron validation, instead of the oxygen native view. On second thought, I guess this thread is a better place to post the question.
I'm wondering whether I could get the SVRL output instead of/in addition to the native error pane display. When I look at Rick J's latest version of the skeleton.xsl pipeline (http://www.schematron.com/implementation.html and in particular the link on that page to iso-schematron-xslt2.zip), I see that he's basically defaulting to SVRL output in any case. As far as I can tell, in oxygen 11.2, there is no option currently to save/view the native SVRL output instead of/in addition to the built-in validation error pane display. This would be very desirable (for me, anyway) in 11.3. (I'm trying to convince a client to put a Schematron validation step in their process pipeline, and they want to know, as well they should, "what's the validation output gonna look like?". The answer is SVRL, but I want to be able to show it to them.) I could just set up a separate transformation scenario using the download from Rick J, but it would be really nice if you could make it a native option in oxygen -- unless it's already there and I'm just like an idiot completely missing it. John On Jun 16, 2010, at 4:06 PM, John Madden wrote: > I'll "third" that vote. > > As I'm sure you also know, George, when there is a "failure to compile > Schematron" error when validating a document with an associated Schematron, > the reported line numbers for the location of the offending statement in the > Schematron are typically off by some (variable) number of lines. I imagine > this relates to the stylesheet pipeline probably transforming the Schematron > first into some canonical representation with potentially different number of > lines. > > John > > On Jun 16, 2010, at 3:21 PM, Lars Huttar wrote: > >> Hello, >> Just "seconding" my own vote here for improved validation of Schematron >> schemas in Oxygen. >> Again today I ran into the problem where Oxygen says the schema is valid, >> but in fact the XPath had a problem. >> In this case, there were two problems: >> >> 1) an XPath expression used a namespace prefix which was included in an >> xmlns: namespace declaration, but was not declared using <sch:ns>: >> <sch:schema xmlns:sch="http://purl.oclc.org/dsdl/schematron"; >> xmlns:svrl="http://purl.oclc.org/dsdl/svrl";> >> ... >> <sch:assert test="$SVRL-results//svrl:failed-assert"> >> >> 2) a rule/@context expression used a variable, which is not allowed (at >> least the generated stylesheet is not valid XSLT): >> <sch:rule context="$original-schema/sch:assert"> >> >> As before, in both cases, the problems were hard to debug because they were >> reported at runtime, after the Schematron schema had been transformed into >> transient XSLT. Strong validation of the schema, catching them at >> schema-editing time, would have made things easier to diagnose and fix. I >> don't suppose there's a Schematron implementation out there that works >> without the XSLT-generation step, and reports validation errors in direct >> reference to the Schematron schema? E.g. Probatron4j (I haven't tried it)? >> >> Thanks... >> Lars >> >> On 5/27/2010 3:58 AM, George Cristian Bina wrote: >>> >>> Dear Lars, >>> >>> Thanks for your feedback! >>> You identified exactly the problem, tracing back the errors to the original >>> schema. Our implementation is based on skeleton, simplified a little as we >>> know the XSLT engine that we use and I also added support for includes and >>> abstract schemas - that means there are a couple of XSLT stylesheets until >>> we get the XSLT from Schematron. I will see what we can do about that, I >>> agree that better validation for Schematron will be a nice thing to have in >>> oXygen. >>> >>> Best Regards, >>> George >> >> _______________________________________________ >> oXygen-user mailing list >> oXygen-user@oxygenxml.com >> http://www.oxygenxml.com/mailman/listinfo/oxygen-user > > _______________________________________________ > oXygen-user mailing list > oXygen-user@oxygenxml.com > http://www.oxygenxml.com/mailman/listinfo/oxygen-user
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
