Uche,

thanks. Actually I didn't mean I was concerned about the maturity of Python, 
I meant the maturity of my team in terms of their ability to support new (at 
least to them) technologies and the risk that this has (or may be perceived 
to have) for operational support.

As a person who has obviously committed time and effort to schemaTron, can 
you say, in your experience, what you think it current usage is like and 
whether you believe that this is likely to grow or be replaced by something 
else ?

I am slightly concerned about the apparent lack of activity both in terms of 
the ISO ratification and the various schemaTron sites/newsgroup/etc...  but 
this may just be an uninformed view.

It appears that there is some sensitive issue that might be delaying this at 
present that Ken Holman hinted at. It is perhaps not tactful to pry into 
specifics but hopefully there will be some sort of progress in the near 
term.

If you hear anything I would be grateful if you would publish to this list.

Cheers

Fraser.


>From: Uche Ogbuji <uche.ogbuji@f...>
>To: Fraser Goffin <goffinf@h...>
>CC: xml-dev@l...
>Subject: Re: [xml-dev] ISO schemaTron
>Date: Sat, 03 Dec 2005 09:05:56 -0700
>
>On Sat, 2005-12-03 at 15:25 +0000, Fraser Goffin wrote:
> > 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.
>
>I see.  I forgot.
>
> > 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).
>
>Not at all cheeky.  Different people have different requirements.  I
>disagree with your group's opinion of Python's maturity.  It's well
>proven in enterprise settings (ask Google, for example), but I also
>understand that some perceptions are slow to change.
>
>Unfortunately, I only know of my Python implementation and a .NET
>implementation of ISO Schematron, so I can't help with a Java offering.
>I've heard there is supposed to be an experimental Java impl based on
>Jaxen (jaxen.org)), but I've never actually found an actual project home
>page for such a schematron component.
>
>
>--
>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>
>