The import thing to realize is that bSAM is not able to check semantics so inevitably licenses that are derived from each other will match have a similarity.
I believe that the returned list is ordered by degree of match; if those % appeared in the table that might be helpful augmentation. But if you don't have a 100% match you need to validate that the difference doesn't change the semantics. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Mark Donohoe Sent: Friday, February 12, 2010 9:49 AM To: Halil Bilda Cc: [email protected] Subject: Re: [FOSSology] License-Count of Fossology Halil Bilda wrote: > Hi Bob, > > now I have a big problem, FOSSology shows a list of licenses, such as > 7 licences in jcommons (attached as a picture). jcommon is Licensed > under LGPL. My products can contain much open source components. I > must check everything manually. Why don't FOSSology show me the > correct license, for example: jcommon -> LGPL but not jcommon-->LGPL, > GPL........ > > Thanks, > Halil > Halil, Yes, we are aware of this issue. Identifying licenses is hard! In our next release we will have another license agent that does a better job in these cases than our current license analyzer. Let me make sure I understand your concern. - You know there is one license. So why do we show 7? is that right? You would like to just see 1 license if there is only one license. Is that right? One of the problems is that there is no standard official license text. People routinely construct a license from the text parts they like or they take a license text that may or may not match the current license distributed on the gnu site. So it is possible that a given license text can match parts of a number of licenses. I know this doesn't help you much, but today, it's the best we can do. We continue to work on license analysis and plan to improve the accuracy as best we can. In this case since you know the license, the match is 'close enough' for that particular file. I would encourage you to use the tool and then look for licenses that are not lgpl/gpl and only focus on those files? Perhaps that might work for you. Hope that helps some. -- Mark Donohoe OS&T, Cupertino CA. fossology.org _______________________________________________ fossology mailing list [email protected] http://fossology.org/mailman/listinfo/fossology _______________________________________________ fossology mailing list [email protected] http://fossology.org/mailman/listinfo/fossology
