Hi,

I've got some short questions about the NOMOS scan engine of version 2.40, 
because I'm not quite sure if I did understand the general functionality 
correctly (I'm not a C expert):


-          The NOMOS engine uses a lot of if-then-else-statements to check 
whether license-texts / -references or similar are included in a file and marks 
findings accordingly, correct? -> seen in file parse.c

-          These license-texts /-references are defined somewhere in the FOSSY 
database, correct? -> is it the license_ref-table?

-          Is it possible to easily add new license (references) just by adding 
new search pattern texts to this table - WITHOUT adaption of the code?

-          Does the NOMOS engine only scan for "standard OSS licenses" - are 
legal relevant phrases scanned by a different agent? (-> regexscan)?

-          Is it possible to easily add new search phrases to Fossology (e.g. 
add new search pattern to a table in the database) - WITHOUT adaption of the 
code?

I'm currently researching the functionality of different OSS scan engines for a 
possible project solution.

I would be happy to hear from you.

Thanks and Regards
Christian

Christian Müller | Senior Consultant
Application & Development
Avanade Deutschland GmbH | Office Kronberg
Campus Kronberg 7
D- 61476 Kronberg
Mobile: +49 (151) 544 121 67
www.avanade.com<http://www.avanade.com/>

Geschäftsführer: Andrew J. Smith, Andrew J. White, Dharmesh Patel, Kenneth 
Allen Guthrie, Pamela Ann Maynard
Amtsgericht Königstein, HRB 6007

[cid:[email protected]]

Join us online

[cid:[email protected]]<https://www.facebook.com/AvanadeGermany> 
[cid:[email protected]] <https://twitter.com/AvanadeASG>  
[cid:[email protected]] 
<https://www.xing.com/companies/avanadedeutschlandgmbh>  
[cid:[email protected]] <http://www.youtube.com/user/AvanadeInc>  
[cid:[email protected]] <http://www.avanade.com/blog>  
[cid:[email protected]] 
<https://plus.google.com/104486611390635973353/posts>

[cid:[email protected]]<http://www.avanade.de/>

<<inline: image017.png>>

<<inline: image018.png>>

<<inline: image019.png>>

<<inline: image020.png>>

<<inline: image021.png>>

<<inline: image022.png>>

<<inline: image023.png>>

<<inline: image024.png>>

_______________________________________________
fossology mailing list
[email protected]
http://lists.fossology.org/mailman/listinfo/fossology

Reply via email to