RE: [egov] Naming and Design Rules for E-Government

["Paul Spencer" <paul.spencer@boynings.co.uk>]

Monica,

Why do you regard Schematron as a tool rather than a standard? It is a
specification, shortly to form part of ISO/IEC 19757. There are validation
tools available (as there are for any schema language), but I use Schematron
by using a transformation from the schema to XSLT (using an XSLT processor),
then the XSLT processor again to validate the input document. So the XSLT
processor is the only tool I require. If I wanted, I could define the XSLT
format, then would not even have to mention Schematron - presumably your
other standard is having to define its own XSLT format rather than use
something that is widely used and will shortly be an ISO/IEC standard. When
I did the research, I found that Schematron was much easier to use than XSLT
directly in this context (not surprising as it was designed for the purpose,
whereas XSLT was not).

Regards

Paul

> -----Original Message-----
> From: Monica J. Martin [mailto:Monica.Martin@Sun.COM]
> Sent: 22 January 2004 15:52
> To: Paul Spencer
> Cc: Michael Bang Kjeldgaard; egov@lists.oasis-open.org
> Subject: Re: [egov] Naming and Design Rules for E-Government
>
>
>
> >Spencer: My approach has therefore been to use XML Schema to
> define the international
> >standard, then Schematron to add constraints to form a national standard.
> >This is the approach we used within OASIS for the Election
> Markup Language.
> >We have been using this successfully in the UK and it will shortly be
> >adopted in many other countries. The approach is to define the
> international
> >standard using XML Schema, then the national standard using
> Schematron *just
> >to indicate the additional constraints*. The Schematron forms
> the normative
> >definition of the constraints (and has the additional advantage
> that it can
> >express constraints that XML Schema cannot) but it is then up to
> >implementers whether they implement this two-stage validation or
> choose some
> >other mechanism. I have implemented a validator that checks EML messages
> >first to the international standard, then the additional national
> >constraints.
> >
> >
> mm1: Paul, one point of reference. One other standard's effort of which
> I am involved, has decided to use XSL transformation instead Schematron,
> mainly because a standard should be based (if needed) on other standards
> not tools. Food for thought. Thanks.
>
> >.....
> >The description of the EML UK Customization and the Schematron schemas
> >themselves can be downloaded from
> >http://www.govtalk.gov.uk/schemasstandards/agreedschema_schema.as
> p?schemaid=
> >201.
> >
> >Regards
> >
> >Paul Spencer
> >Director
> >Boynings Consulting Ltd
> >http://www.boynings.co.uk
> >
> >
>
>
> To unsubscribe from this mailing list (and be removed from the
> roster of the OASIS TC), go to
> http://www.oasis-open.org/apps/org/workgroup/egov/members/leave_wo
> rkgroup.php.
>
>