Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xml-dev] A single, all-encompassing data validation language - good or bad for the marketplace?

From: "Chris Scott" <scott.chris@-----.--->
To: "Fraser Goffin" <goffinf@----------.--->
Date: 8/7/2007 6:26:00 PM
On 8/7/07, Fraser Goffin <goffinf@g...> wrote:
> I seem to recall that the approach to embedding schematron rules directly
> into W3C schema have been somewhat defined already, although of course I'm
> not sure whether there are validating parsers support this style natively (I
> have the feeling that Daniel Cazzulino's schemaTron.Net used to, but I'm not
> sure what happened to this implementation).

Thanks for reminding me of that link. There's a handy stylesheet
(XSD2Schtrn.xsl), included with that article that allows you to pull
out the embedded schematron and run the validation in a two step
process.  I built a handy library a bit back to use the iso_skeleton
and the aforementioned stylesheet to use xsd+schematron but it always
felt like a hack and I never put it into a production system.  (Look
at all of the transformations! 3 transformations just for the
schematron step)

Using I'd argue against embedding schematron elements using
//xs:annotation/xs:appinfo/ if schematron is included in the spec,
mostly for the sake of brevity.  Since we'd change the existing spec,
we wouldn't have to worry about it needed to be in appinfo.  I'd also
argue against embedding anywhere in the grammar definition, but I'm
going to follow up on that in another post.

~Chris


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent