<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hey George et al.,<div><br></div><div>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.</div><div><br></div><div>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 (<a href="http://www.schematron.com/implementation.html">http://www.schematron.com/implementation.html</a> and in particular the link on that page to <a href="http://www.schematron.com/tmp/iso-schematron-xslt2.zip">iso-schematron-xslt2.zip</a>), I see that he's basically defaulting to SVRL output in any case.</div><div><br></div><div>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.)</div><div><br></div><div>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.</div><div><br></div><div>John</div><div><br></div><div><br><div><div>On Jun 16, 2010, at 4:06 PM, John Madden wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I'll "third" that vote.<div><br></div><div>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.</div><div><div><br></div><div>John</div><div><br><div><div>On Jun 16, 2010, at 3:21 PM, Lars Huttar wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<div bgcolor="#cccccc" text="#000000">
Hello,<br>
Just "seconding" my own vote here for improved validation of Schematron
schemas in Oxygen.<br>
Again today I ran into the problem where Oxygen says the schema is
valid, but in fact the XPath had a problem.<br>
In this case, there were two problems:<br>
<br>
1) an XPath expression used a namespace prefix which was included in an
xmlns: namespace declaration, but was not declared using <sch:ns>:<br>
<sch:schema xmlns:sch=<a class="moz-txt-link-rfc2396E" href="http://purl.oclc.org/dsdl/schematron">"http://purl.oclc.org/dsdl/schematron"</a><br>
xmlns:svrl=<a class="moz-txt-link-rfc2396E" href="http://purl.oclc.org/dsdl/svrl">"http://purl.oclc.org/dsdl/svrl"</a>><br>
...<br>
<sch:assert test="$SVRL-results//svrl:failed-assert"><br>
<br>
2) a rule/@context expression used a variable, which is not allowed (at
least the generated stylesheet is not valid XSLT):<br>
<sch:rule context="$original-schema/sch:assert"><br>
<br>
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)?<br>
<br>
Thanks...<br>
Lars<br>
<br>
On 5/27/2010 3:58 AM, George Cristian Bina wrote:
<blockquote cite="mid:4BFE3428.7000508@oxygenxml.com" type="cite">Dear
Lars,
<br>
<br>
Thanks for your feedback!
<br>
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.
<br>
<br>
Best Regards,
<br>
George
<br>
</blockquote>
<br>
</div>
_______________________________________________<br>oXygen-user mailing list<br><a href="mailto:oXygen-user@oxygenxml.com">oXygen-user@oxygenxml.com</a><br><a href="http://www.oxygenxml.com/mailman/listinfo/oxygen-user">http://www.oxygenxml.com/mailman/listinfo/oxygen-user</a><br></blockquote></div><br></div></div></div>_______________________________________________<br>oXygen-user mailing list<br><a href="mailto:oXygen-user@oxygenxml.com">oXygen-user@oxygenxml.com</a><br>http://www.oxygenxml.com/mailman/listinfo/oxygen-user<br></blockquote></div><br></div></body></html>