Subject: Re: [xsl] license file for Saxon|
From: Roger I Martin PhD <hypernexdev@xxxxxxxxxxxxxxx>
Date: Mon, 12 Dec 2005 13:01:13 -0500
Such questions really don't belong on the xsl-list, but I'll answer anyway.
If you don't want to include the full Saxon documentation in your product, I suggest you include the text from the two files doc/conditions/index.html and doc/conditions/other.html. This contains a reference to the MPL 1.0 license on the web, which I think is adequate.
It's probably better to include saxon8.jar in your distribution to avoid any version compatibility problems, though you should make it possible for users who know what they are doing to substitute a later version (so long as it works). Of course if all your users are very techie (e.g. if they have to build the product themselves) then you might prefer them to do their own download.
There's never been a Saxon logo as such - I resisted it as I always felt it had too much of a commercial feel to it. Just make sure the product is mentioned by name. Don't use the Saxonica logo, as I don't want people imagining that there's some kind of relationship or partnership with the company.
Michael Kay http://www.saxonica.com/
From: Roger I Martin PhD [mailto:hypernexdev@xxxxxxxxxxxxxxx] Sent: 12 December 2005 17:02
Subject: [xsl] license file for Saxon
A question for Michael Kay
After downloading Saxon from Sourceforge I don't find a license file to include with it in my two opensource sourceforge projects. Would it be better to make an Ant Script download Saxon from its location for users to get it rather than put saxon8.jar in my projects lib folder? Should I be adding the MPL license?
Also is there a perferred Saxon logo to include in software welcome and info pages? Saxonica_logo.*?