Oh...



> Open source?



Yes.  Saxon.NET 8.x-B implements the same licensing mechanism that Saxon 8.x-B 
implements (the Mozilla Public License Version 1.0) with the simple addition 
that any changes or updates to the Saxon.NET source code have been provided by 
the x2x2x.org community and to please include a reference to the x2x2x.org 
community in any .NET project (commercial or non-commercial) that utilizes the 
x2x2x.org implementation of Saxon via Saxon.NET.  Saxon.NET 8.x-B is completely 
Open-Source just as Saxon 8.x-B from Dr. Michael Kay and Saxonica is Open-Source.



Versions of Saxon.NET-SA will be released according to the licensing guidelines 
set forth via Saxonica and will be completely compliant with all versions of the 
.NET CLR that adhere to the standards set forth by the ECMA, the governing body 
in which Microsoft, Intel, and Hewlett-Packard submitted the Common Language 
Infrastructure and C# programming language to for standardization in August of 
the year 2000.



More information regarding the Saxon.NET project can be found at 
http://www.x2x2x.org/x2x2x/home or at the SourceForge.net project page located 
at http://sourceforge.net/projects/saxondotnet/



Hope this helps answers your question!



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