Hi, I feel that the ECW discussion between Edgar and Stephan has gone to the fundamental level and both are going to keep their minds. My conclusions are - The company ER Mapper defended itself successfully in the patent struggle against LizardTech but lost still all the money so it got bought by Leica (this is my personal view). - Leica changed the license policy but the company could not take back what was already released. - However, they do not need to continue to deliver the ER Mapper era stuff, and they don't. - The version 3.x SDK from ER Mapper can be still used under the 3.x license. - It is hard to solve the obscurities in the 3.3 license because there seems to be nobody left on the other side to interpret what was the meaning of ER Mapper. - However, the decompression side was unlimited in all the licensing alternatives and OpenJUMP cannot compress so OpenJUMP is under the ECW JPEG 2000 SDK FREE USE LICENSE AGREEMENT stating "The intent of this license is to allow unlimited decompression and limited compression (500MB per image) of ECW JPEG 2000 images within free or commercial applications." - Stephan does not want to include ecw binaries in his builds and it is OK, he does not need to. - Ede is convinced that he is allowed to include ecw binaries in his builds.
I share Ede's opinion but to be sure ERDAS should either say it is OK or sue us so that the issue would be weighted at the court. -Jukka Rahkonen- > -----Alkuperäinen viesti----- > Lähettäjä: Stephan Holl [mailto:stephan.h...@intevation.de] > Lähetetty: 7. lokakuuta 2011 16:19 > Vastaanottaja: OpenJump develop and use > Aihe: Re: [JPP-Devel] ecw licensing is no issue > > Hello ede, > > edgar.sol...@web.de, [20111007 - 11:21:10] > > > First and foremost, there is _no_ license issue here. We have two > > licenses, to which terms we have to agree and act. > > I could not find the place where I could get the SDK dlls (version > 3.3) for Download for free. It would be good if you could provide a > link where the files came from. > > Current ERDAS-website does apparently does not host it (any more?). > > I would like to see the dlls excluded in the nightlies and provided in > a separate package if one likes to use them. Additionally, > this version > only allows the compression and decompression of files <500MB. Who is > checking this with this binary build? > > Looking at the GDAL/QGIS-folks the do not distribute any > binadary-build > using ECW; however, building from source is surely available, but the > enduser must download an SDK - after aggreeing a licence term. > > Again, I would strongly vote for excluding the ecw-binaries and adding > a hint to the enduser, that ECW-dlls are available and only need to be > placed at some place to make OJ happily using it though. > > another 0.02¢. > > Best > > Stephan > > > > ECW SDK license (note: version 3.3): > > For everyone unsure i attached the license of the ecw code used to > > this email. Our use case is the first license in there: --> > > Use of the ECW JPEG 2000 SDK with Unlimited Decompressing and > > Unlimited Compression for applications licensed under a GNU General > > Public style license ("GPL") is governed by the "ECW JPEG 2000 SDK > > PUBLIC USE LICENSE AGREEMENT". <-- The only drawback would be some > > commercial restriction "selling,renting not allowed", but this > > shouldn't be our concern, because we do _nothing_ of that sort and > > anyone who wants to should make sure to oblige _all_ licenses. > > > > GPL2: > > Secondly there is the GPLv2, the oj license. Everybody can > get a copy > > themselves. in a nutshell it protects every code based on > gpl code by > > extending gpl to it. This actually does not prevent you to use > > libraries or other software with it. It "merely" insists on proper > > interfaces, which make sure that these are independent software > > parts. This can be problematic, because a lot of interfacing in some > > programming languages is done by definitions, which are done in > > source code themselves. So actually if a library would include this > > code, it would need to be gpl'd again. But this is not the > case here. > > There is a clean separation of the source code and oj is > merely using > > ecw routines, not the other way around. This is covered by the > > "plugin" definition. > > http://www.gnu.org/licenses/gpl-faq.html#GPLAndPlugins > > > > in conclusion, no problem here. > > > > ..ede > > > > -- > Stephan Holl <stephan.h...@intevation.de> | Tel.: +49 > (0)541-33 508 3663 > Intevation GmbH, Neuer Graben 17, 49074 OS | AG Osnabrück - > HR B 18998 > Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. > Jan-Oliver Wagner > ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2 _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
