RickRegards* for each error on that node, generate an svrl:failed-assert element, and provide a link to the XSD documentation for the particualr error in the @see attribute, and just false() as the assertion, and some assertion text of whatever usefulness you can extract: maybe just "The document should be valid aginst the XSD schema" if the implementation provides no text. (You may be able to fill in @role too.)* for each node that has an error in the PSVI, generate an svrl:fired-rule, and provide the XPath and/or linenumber in attributes* make an svrl:active-pattern element to hold the XSD validation resultsAnd I do have a more concrete suggestion: you should be able to convert the output of the XSD validator into SVRL and merge it with the real SVLR. This is code you would have to write, for a particular validator.You would do something like this:On Wed, Mar 8, 2017 at 7:30 PM, Frank Steimke <f-steimke@berger-und-steimke.de > wrote:
Hi,
validation of XML-based business documents is often a process with two ore more phases:
a) check structure against XSD or RELAX NG Schema;
b) check additional constraints against Schematron
In typical scenarios the user would like to inspect validation results before he decides about further processing. In order to support automatic inspection as well as logging the incoming trafic, we would like to have the validation report to be a single XML document, which combines all the neccessary information from the validations that took place. We also would like to have extension points for additional, user specific validation, for example electronic signatures or certificates.
So my question to this list is: is there any generic Schema Validation Report Language out there which can act as Schema for reports in this scenario? I'm quite aware of the Schematron Validation Report Language (Annex D of ISO/IEC 19757-3:2016), but this is restricted to Schematron.
Closely related to this question is another one: is it a requirement for every W3C Schema validation engine to report schema errors and validation failures in terms of appendix C "Outcome Tabulations" of XML Schema Part 1: Structures, together with a error location in a standardized way? Does this also hold for relax NG engines (although i know only one ...).
Thanks in advance,
Frank Steimke
____________________________________________________________ ___________
XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.
[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
subscribe: xml-dev-subscribe@lists.xml.org
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php