Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xml-dev] schematron for xml schema validation

From: bryan rasmussen <rasmussen.bryan@-----.--->
To: Paul Spencer <xml-dev@--------.--.-->
Date: 1/6/2006 10:16:00 AM
Hi Paul,
Sounds interesting and like a reasonable subject for a presentation,
but what I meant by "controlling the Schematron
 elegantly across a set of schemas" was the need to control Schematron
behavior across a set of XML Schemas, i.e. the external documents
requirement but from the starting point of being able to define a set
of xml schemas to operate across and having the schematron schemas
applied across the set but also interact within the set - perhaps via
an extension mechanism or by having a dsl for controlling the sets. I
have actually received a mail that was close to my requirements, but
it was not publically sent to xml-dev. maybe not ready for announcing
their project yet.

Cheers,
Bryan Rasmussen

On 1/6/06, Paul Spencer <xml-dev@b...> wrote:
> I have used Schematron for tailoring XML schemas for specific requirements.
> I came across this defining specifications for using the Election Markup
> Language for messages between electoral registers in the UK. There was no
> need to access external documents, so I can't help there, but I had to
> produce 15 Schematron schemas, each using a subset of a larger set of rules.
> I think that this might be what you mean by "controlling the Schematron
> elegantly across a set of schemas".
>
> I did this by defining each of the rules in a spreadsheet (with columns for
> rule, context, assert/report etc), then having a column for each of the 15
> message types saying whether that rule applied. I then used a macro to
> generate some simple XML from this and then a stylesheet to produce the 15
> Schematron schemas under the control of a simple ASP script. I expect a real
> programmer could find a better way. Apart from the ease of only modifying a
> single spreadsheet for any changes, this had the advantage that the
> spreadsheet was much easier for the software suppliers that would be using
> the Schematron to understand.
>
> I have submitted this as a case study for XTech 2006.
>
> Regards
>
> Paul Spencer
>
> > -----Original Message-----
> > From: bryan rasmussen [mailto:rasmussen.bryan@g...]
> > Sent: 04 January 2006 13:08
> > To: xml-dev@l...
> > Subject: [xml-dev] schematron for xml schema validation
> >
> >
> > Hey
> > I'm doing a little schematron for validation of spec required xml
> > schema structure, some of the validation rules cannot be done by
> > schematron itself as it involves doing validation across external
> > documents (I am focusing on a schematron that will work in all
> > implementations so use of document function etc. not doable.)
> >
> > Anybody have experience with this problem, ideas for controlling the
> > schematron elegantly across a set of schemas?
> >
> > -----------------------------------------------------------------
> > The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> > initiative of OASIS <http://www.oasis-open.org>
> >
> > The list archives are at http://lists.xml.org/archives/xml-dev/
> >
> > To subscribe or unsubscribe from this list use the subscription
> > manager: <http://www.oasis-open.org/mlmanage/index.php>
> >
>
>


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