Hi Kotrappa, This was best explained by our friend Silvano in http://www.fossology.org/issues/6957
Thanks, Bob Gobeille On Apr 30, 2014, at 11:17 PM, <[email protected]> <[email protected]> wrote: > Hello Larry, Bob > > Could you please explain below statement > > >> Right now, FOSSology cannot differentiate between containing a license and >> released under a license, we are >sorry for that. > > > what is the meaning of containing a license and released under a license. > > What i think is "released under a license" - is user can derive the source > code, modify it, embed his own license text, but his binary or package > should contain original license text in the form of document say like > COPYING etc.??? > > The meaning of "containing license" - the source which contains original > license itself. > > Let us know if this is correct. > > regards > Kotrappa > ________________________________________ > From: Shi, Yao-Bin (Larry, GBU-HPSW, Cloud and OS) [[email protected]] > Sent: Tuesday, April 29, 2014 3:19 PM > To: Ravishankar T.S (WT01 - Manufacturing & Hi Tech); Gobeille, Robert; > Kotrappa DeverShetty (WT01 - Manufacturing & Hi Tech) > Cc: Akanksha Singh (WT01 - Manufacturing & Hi Tech); [email protected] > Subject: RE: [FOSSology] Query on how fossology scans for license and > recogizes the correct license > > Hello Kotrappa, > > How FOSSology detect licenses. > Let us take a tar ball > http://www.fossology.org/releases/2.5.0/Debian/7.0/fossology_2.5.0-1.tar.gz > as an example. > 1. upload this tar ball via upload from URL > 2. FOSSology will store this tar ball and unpack this tar ball into > individual files reclusively, then store all the files into the repository. > 3. nomos - critical part of FOSSolgoy tool, it will analyze all the > individual files, and report licenses for every single file, for graphical > user interface, you can browse to see which licenses every single > file/directory/packages has via 'License Browser'. > Here I am not saying 'which licenses every single file/directory/package is > released under' is because, right now, FOSSology is trying to report all > detecting licenses, we detect a license through license signature not the > whole license text, actually, most files are not using standard license text, > using derivative license text/license name, so we think using signature to > detect license is a good idea. > Right now, FOSSology cannot differentiate between containing a license and > released under a license, we are sorry for that. > However we can report most licenses(standard license and derivative license) > in a file. > > How nomos works on a file normally, scanning one file, then try to mach all > the signatures in STRINGS.in, report all the licenses nomos found in a file. > a) parse one file content into couple of paragraphs, trim paragraphs(some > special signs, such as '/*' '//') > b) for every single paragraph, trying to match all the signatures(Regular > expression), when matched, report it. > 4) report the detected licenses and store related data into database, user > can see licenses from GUI and CLI. > > Hope it is helpful. > > -Larry > >> -----Original Message----- >> From: [email protected] [mailto:fossology- >> [email protected]] On Behalf Of [email protected] >> Sent: Tuesday, April 29, 2014 12:35 PM >> To: Gobeille, Robert; [email protected] >> Cc: [email protected]; [email protected] >> Subject: Re: [FOSSology] Query on how fossology scans for license and >> recogizes the correct license >> >> Hello Bob, >> >> Thanks a lot for the quick reply. >> >> Can you pls help us to understand in details mechanism of license >> detection process in FOSSology. Pls also, share the documents if you have >> any. >> >> This is critical since we need to provide accurate license reports (we >> have seen many third party supplied files with incomplete notice and >> copyright text but declared to be open source). This helps in >> incorporating additional steps to resolve conflicting license issues. >> >> Regards >> Ravits >> >> >> -----Original Message----- >> From: Gobeille, Robert [mailto:[email protected]] >> Sent: Monday, April 28, 2014 10:29 PMring & Hi Tech) >> Cc: <[email protected]>; Ravishankar T.S (WT01 - Manufacturing & Hi >> Tech); Akanksha Singh (WT01 - Manufacturing & Hi Tech) >> Subject: Re: [FOSSology] Query on how fossology scans for license and >> recogizes the correct license >> >> Hello Kotrappa, >> >> Your investigation into the license scanner is correct but be aware that >> the scanner does not look for an entire license notice or license text. >> It only looks for signatures (see file STRINGS.in). So a file could >> contain a license that is missing pieces and the scanner may not notice. >> For example, in the BSD-2-Clause, if you remove the entire paragraph "THIS >> SOFTWARE IS PROVIDED ...", nomos will still identify the file as BSD-2- >> Clause. However, if you remove either of the two conditions, nomos will >> report "BSD-style". >> >> Does that answer your question? >> >> Thanks, >> Bob Gobeille >> >> >> On Apr 28, 2014, at 6:25 AM, <[email protected]> >> <[email protected]> wrote: >> >>> +my team >>> ________________________________________ >>> From: Kotrappa DeverShetty (WT01 - Manufacturing & Hi Tech) >>> Sent: Monday, April 28, 2014 5:34 PM >>> To: Gobeille, Robert >>> Cc: [email protected] >>> Subject: RE: [FOSSology] Query on how fossology scans for license and >>> recogizes the correct license >>> >>> Hello Bob, >>> >>> This is regarding discussion on internal logic/operation about FOSSology >> tool on how it determines License for a file. >>> we investigated and verified that FOSSology scans for a "License Notice >> text" of a license for e.g. say take BSD-2-Clause licenses, it scans for >> copyright info followed by license notice text. If it recognizes the match, >> then it declares the license of particular file as BSD-2-Clause. >>> My question is what if you have missed two-or more lines from "notice >> text", does FOSSology recognize correctly as BSD-2-Clause?? Let us know if >> there is a workaround? some thing having checksum of same file in a >> database or recognizing logical pattern etc. >>> >>> --- >>> http://spdx.org/licenses/BSD-2-Clause#licenseText >>> Copyright (c) <YEAR>, <OWNER> >>> All rights reserved. >>> Redistribution and use in source and binary forms, with or without >> modification, are permitted provided that the following conditions are met: >>> >>> 1) Redistributions of source code must retain the above copyright notice, >> this list of conditions and the following disclaimer. >>> >>> 2) Redistributions in binary form must reproduce the above copyright >> notice, this list of conditions and the following disclaimer in the >> documentation and/or other materials provided with the distribution. >>> >>> THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS >>> "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT >> LIMITED TO ..... >>> ... >>> --- >>> >>> regards >>> Kotrappa. >>> >>> >>> >>> The information contained in this electronic message and any attachments >> to this message are intended for the exclusive use of the addressee(s) and >> may contain proprietary, confidential or privileged information. If you >> are not the intended recipient, you should not disseminate, distribute or >> copy this e-mail. Please notify the sender immediately and destroy all >> copies of this message and any attachments. >>> >>> WARNING: Computer viruses can be transmitted via email. The recipient >> should check this email and any attachments for the presence of viruses. >> The company accepts no liability for any damage caused by any virus >> transmitted by this email. >>> >>> www.wipro.com >> >> >> The information contained in this electronic message and any attachments >> to this message are intended for the exclusive use of the addressee(s) and >> may contain proprietary, confidential or privileged information. If you >> are not the intended recipient, you should not disseminate, distribute or >> copy this e-mail. Please notify the sender immediately and destroy all >> copies of this message and any attachments. >> >> WARNING: Computer viruses can be transmitted via email. The recipient >> should check this email and any attachments for the presence of viruses. >> The company accepts no liability for any damage caused by any virus >> transmitted by this email. >> >> www.wipro.com >> _______________________________________________ >> fossology mailing list >> [email protected] >> http://lists.fossology.org/mailman/listinfo/fossology > > The information contained in this electronic message and any attachments to > this message are intended for the exclusive use of the addressee(s) and may > contain proprietary, confidential or privileged information. If you are not > the intended recipient, you should not disseminate, distribute or copy this > e-mail. Please notify the sender immediately and destroy all copies of this > message and any attachments. > > WARNING: Computer viruses can be transmitted via email. The recipient should > check this email and any attachments for the presence of viruses. The company > accepts no liability for any damage caused by any virus transmitted by this > email. > > www.wipro.com _______________________________________________ fossology mailing list [email protected] http://lists.fossology.org/mailman/listinfo/fossology
