Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xsl] xslt 2.0 and alternatives?

From: "M. David Peterson" <m.david@---------->
To:
Date: 10/2/2004 1:53:00 AM
Absolutely!  Dr. Kay's suggestion is the best for your particular situation.



> I'm not interested in anything MS-specific myself.  The whole point of
> what I'm doing is to provide alternatives to MS-centric workflows (the
> academy is totally dominated by MS, and I'm tired of it).  So document
> formats I'm interested in are DocBook, TEI, OpenOffice.

And I don't in any way blame you.  In fact, I myself (even with my MS dominant 
background) have been looking to alternatives to the MS dominant workplace and 
have *REALLY* (if not apparent, let me emphasize REALLY!!!) taken a liking to 
the offerings from Novell, Gnome, and the Mono project... The interface is clean 
(kudo's to the Gnome team for creating such a fantastically clean, simple, and 
beautiful GUI!!!), the .NET CLR implementation solid (kudo's to Miguel de Icaza 
and his passion for bringing the .NET CLR and the C# language to the Open-Source 
Linux community), and the overall effort by the Linux Open-Source community is 
overwhelming and has subsequently drawn me in to using there developed platform 
about 50-60% of the time I spend in front of my computer (which is between 14-16 
hours, at least, a day.)  And that doesn't even touch the whole OpenOffice 
project which most definitely deserves an entire email of praise devoted to 
everything that they have brought to the XML table and then some.



With all of this said (and your recommendation that people pick this up for use 
with Word/WordML) I would recommend that people seriously consider the fact that 
Saxon, Saxon.NET, OpenOffice.org and a complete array of XML technologies that 
would take pages to showcase are 100% completely supported by the Linux platform 
and in the case of Saxon.NET and C# (as well as a beta version of VB.NET) are 
supported via the Mono mechanism that you can learn more about at 
http://www.go-mono.com.



I hope that anyone with an open mind to alternatives will take a look at what an 
 *AMAZING* group of very committed developers have brought, FOR FREE!!!!, to 
the software development community and how these elements are 100% compliant 
with the standards that we, as an XML community, have asked for.



Best regards,



<M:D/>



Bruce D'Arcus wrote:
Thanks David!



On Oct 2, 2004, at 11:03 AM, M. David Peterson wrote:



But let me first preface this with the following... The goal of the 
Saxon.NET project is to provide to the .NET community an API that is 
100% compliant with that of Dr. Michael Kay's latest Saxon API and 
that can be used to implement a XSLT 2.0, XPath 2.0, and XQuery 1.0 
transformation via any language and subsequent compiler that 
implements a solution supported by version 1.1+ of the ..NET framework.




I'm not interested in anything MS-specific myself.  The whole point of 
what I'm doing is to provide alternatives to MS-centric workflows (the 
academy is totally dominated by MS, and I'm tired of it).  So document 
formats I'm interested in are DocBook, TEI, OpenOffice.



If others want to pick this up for integration with Word/WordML, though, 
that'd be good, so it's nice to have Saxon.NET as an alternative.  I'm 
thinking Mike's suggestion of a web service is sounding like the best 
medium-term solution, though.



If not now, there will be XSLT 2.0 solutions, via your desired 
mechanism, in the months, not years, to come.




Open source?



Bruce


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