W3C home > Mailing lists > Public > public-xsd-databinding@w3.org > June 2006

RE: ISSUE-12 identifying conformant schemas

From: George Cowe <gcowe@origoservices.com>
Date: Tue, 6 Jun 2006 16:44:06 +0100
Message-ID: <DC65AE678B89004B9CCB202E19482CC7013AC6B6@mail.origoservices.local>
To: public-xsd-databinding@w3.org
Attached are some schematron files which I created in an attempt to identify basic patterns in the examplexsd.xsd file.

It works against using Saxon 8 as the processor.

 

Three approaches which correspond to the patternRules files. 

1) use the "one schematron pattern per schema pattern" approach which seems to work best.

2) just use one schematron pattern with one rule (context of root) and multiple reports/asserts. This behaves in the same way as the "one schematron pattern per schema pattern" approach but only reports/asserts the first occurrence of a schema pattern. Which means you don't get information about the individual complexType/simpleType/element which is firing the rule.

3) just use one schematron pattern with multiple rules (one for each schema pattern).  The problem here is that only the first rule matched is fired so it's pretty useless! This also seems to be the only sensible way to use the catch all @*|* rule unless I'm mistaken.

 

This simply allows a list of patterns that have been detected to be listed. What we really want is a list of patterns that are detected as not being present in the basic patterns and highlight these as an issue. How do you do that without actually looking specifically for them? 

 

 






Received on Tuesday, 6 June 2006 20:28:59 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 18:20:37 GMT