Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xml-dev] ISO schemaTron

From: "Fraser Goffin" <goffinf@-------.--->
To: xml-dev@-----.---.---
Date: 12/3/2005 3:26:00 PM
Uche,

no I am not constrained to using XSLT per se but I do prefer it because of 
its portability.

You kindly pointed me at your Scimitar implementation when answering another 
schemaTron question for me a while back and I did download it and talk to 
some of my design colleagues. Our (current) opinion which is partly based on 
our level of maturity and the technology policy of our organisation, was 
that we couldn't really contemplate the implementation of critical aspects 
of enterprise applications based on a technology we know so little about and 
have virtually no skills in (I know you said you don't need to know Python, 
but I'm not just talking about development skills, its operational support 
for the live environment which is typically our major issue). I would 
definately consider a Java implementation of ISO SchemaTron if you know of 
one (sorry I know thats a bit cheeky given your Amara implementation, but 
schemaTron seems to be losing a little bit of traction, so all publicity is 
good).

Fraser.


>From: Uche Ogbuji <Uche.Ogbuji@f...>
>To: xml-dev@l...
>Subject: Re: [xml-dev] ISO schemaTron
>Date: Thu, 01 Dec 2005 18:27:14 -0700
>
>On Wed, 2005-11-23 at 07:39 -0500, G. Ken Holman wrote:
> > At 2005-11-23 12:13 +0000, Fraser Goffin wrote:
> > >Does anyone have an update on schemaTron ISO ratification ?
> >
> > ISO/IEC 19757-3 Schematron is currently past the FCD stage and is
> > awaiting the next FDIS stage as indicated in the up-to-date committee
> > Secretariat Report that is publicly viewable at all times:
> >
> >   http://www.jtc1sc34.org/document/secretariat_temp.html#matrix  (a 
>large page)
> >   http://www.jtc1sc34.org/document/secretariat_temp.html#is19757-3
> >
> > >I currently use the XSLT reference implementation for 1.5, but like
> > >many others I suspect, am very interested in some of the proposed
> > >new features such as abstract patterns, let and include.
> >
> > I found a bug in the 1.5 implementation w.r.t. using attributes as a
> > context, so I've posted a modified version of 1.5 here:
> >
> >    http://lists.oasis-open.org/archives/ubl/200511/msg00103.html
> >
> > >If my XSLT skills were better I might have a go at creating new
> > >'skeleton' and XML ouput implementations, but alas they are not
> > >really up to it.
> >
> > Would that any of us could make the time to do so.
> >
> > >Does anyone out there have plans to produce an ISO XSLT
> > >implementation any time soon :-) ??
>
>Wot Ken said across the board, but I did want to ask whether you are
>constrained to use XSLT.  There are some non-XSLT implementations
>available based on the ISO drafts, including the desired features you
>mentioned.  I should know because I've written one of them: Scimitar
>(part of Amara [1]).  Scimitar is implemented in Python, but you don't
>have to be a Python programmer to use it: you can just run it from the
>command line on most platforms.
>
>[1] http://uche.ogbuji.net/tech/4suite/amara/
>
>--
>Uche Ogbuji                               Fourthought, Inc.
>http://uche.ogbuji.net                    http://fourthought.com
>http://copia.ogbuji.net                   http://4Suite.org
>Articles: http://uche.ogbuji.net/tech/publications/
>
>
>-----------------------------------------------------------------
>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