Re: add markup to Plexus and TCL?
Alexios Zavras
Hi all, happy new year!
Just wanted to make sure the first item below is not forgotten. I have seen the “same” text (with different names for attribution requirements) at: - Dom4j, e.g. http://dom4j.sourceforge.net/dom4j-1.6.1/license.html - Jaxen, e.g. https://confluence.sakaiproject.org/display/LIC/Jaxen+License+1.3 - jCharts, e.g. http://jcharts.sourceforge.net/license.html
Ideally, this would be called “Codehaus license”, but I understand the need for keeping names consistent.
-- zvr
From: spdx-legal-bounces@... [mailto:spdx-legal-bounces@...]
On Behalf Of opensource@...
Sent: Thursday, November 12, 2015 4:07 AM To: spdx-legal@... Subject: add markup to Plexus and TCL?
Hi All,
I’d like to recommend that we add markup around the names in Plexus http://spdx.org/licenses/Plexus.html - dom4j uses the same license, but for the names and this is a common project, so it would make sense to be able to match on the substantive text, instead of using a LicenseRef for dom4j.
See dom4j license here: http://sourceforge.net/p/dom4j/code/ci/default/tree/LICENSE.txt
Also, I noticed that the text we have for TCL - http://spdx.org/licenses/TCL.html is not exactly the same as is on the website: http://www.tcl.tk/software/tcltk/license.html I have not done a precise comparison, but it appears the only difference is in the names at the top and could probably be “fixed” by adding some markup.
Thanks, Jilayne Intel Deutschland GmbH |
|