OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] Schema validation Report Language?

And a more general version of your question: is a filter technology that reads in resources (with a standard representation from a location using a URL) but does not write out to a representation that can be potentially located with a URL) really a "web" technology?

In the case of XSLT, it does and so is, for its main input and output. 

But with validator standards, none apart from Schematron SVRL do, and I suggest they should not be categorized as Web technologies.  (And the same goes for XML DTDs for validation, but not attribute-value implication.)   In the case of XSD, it is compounded that the PSVI has no serialized form at all: so not only is the output of validation errors not available as a resource with a concrete standard representation, the PSVI elements that have been successfully validated are not available either.

The consequence: if the both the input and output for a filter are not available with concrete representations that could be at a URL, then the output requires some extra technology or platform to access and process.  So you end up with absurdity of people buying into XML to get loose coupling and distributability, and then finding that XSD PSVI forces you to have tight coupling and large-object sharing.  I think this is a real problem for client/server architecture with XQuery with XSD, because you must throw out the non-XML PSVI information when you send the query results from the server to the client.  That cannot help but to drive people to use JSON.


On Wed, Mar 8, 2017 at 7:30 PM, Frank Steimke <f-steimke@berger-und-steimke.de> wrote:

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

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS