This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
A Method for Open Source License Compliance of Java Applications
May-June 2012 (vol. 29 no. 3)
pp. 58-63
ASCII Text
x 
 
Daniel German, Massimiliano Di Penta, "A Method for Open Source License Compliance of Java Applications," IEEE Software, vol. 29, no. 3, pp. 58-63, May-June, 2012.
 
 
BibTex
x
 
@article{ 10.1109/MS.2012.50,
author = {Daniel German and Massimiliano Di Penta},
title = {A Method for Open Source License Compliance of Java Applications},
journal ={IEEE Software},
volume = {29},
number = {3},
issn = {0740-7459},
year = {2012},
pages = {58-63},
doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2012.50},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - MGZN
JO - IEEE Software
TI - A Method for Open Source License Compliance of Java Applications
IS - 3
SN - 0740-7459
SP58
EP63
EPD - 58-63
A1 - Daniel German,
A1 - Massimiliano Di Penta,
PY - 2012
KW - open source
KW - copyright
KW - licensing
KW - provenance
KW - legal compliance
VL - 29
JA - IEEE Software
ER -
 
Daniel German, University of Victoria
Massimiliano Di Penta, University of Sannio
Open source license compliance (OSLC) is the process of ensuring that an organization satisfies the licensing requirements of the open source software it reuses, whether for its internal use or as a part of a product it ships. The major challenges of OSLC include component identification, provenance discovery, license identification, and licensing requirements analysis. Kenen is an approach that assists organizations in OSLC for Java components.

1. D.M. German and A.E. Hassan, “License Integration Patterns: Addressing License Mismatches in Component-Based Development,” Proc. 31st Int'l Conf. Software Eng. (ICSE 09), IEEE CS, 2009, pp. 188–198.
2. M. Di Penta et al., “An Exploratory Study of the Evolution of Software Licensing,” Proc. 32rd Int'l Conf. Software Eng. (ICSE 10), IEEE CS, 2010, pp. 145–154.
3. D.M. German, Y. Manabe, and K. Inoue, “A Sentence-Matching Method for Automatic License Identification of Source Code Files,” Proc. IEEE/ACM Int'l Conf. Automated Software Eng. (ASE 10), ACM, 2010, pp. 437–446.
4. D.M. German, M. Di Penta, and J. Davis, “Understanding and Auditing the Licensing of Open Source Software Distributions,” Proc. 18th Int'l Conf. Program Comprehension (ICPC 10), IEEE CS, 2010, pp. 84–93.
5. J. Davies et al., “Software Bertillonage: Finding the Provenance of an Entity,” Proc. Working Conf. Mining Software Repositories (MSR 11), ACM, 2011, pp. 183–192.
6. C. Ruffin and C. Ebert, “Using Open Source Software in Product Development: A Primer,” IEEE Software, vol. 21, no. 1, 2004, pp. 82–86.
7. M. Sojer and J. Henkel, “Code Reuse in Open Source Software Development: Quantitative Evidence, Drivers, and Impediments,” J.Association for Information Systems, vol. 11, no. 12, 2010, article 2.
8. M. Sojer and J. Henkel, “License Risks from Ad Hoc Reuse of Code from the Internet,” Comm. ACM, Dec. 2011, pp. 74–81.
9. N.J. Mertzel, “Copying 0.03 Percent of Software Code Base Not 'De Minimis,'” J. Intellectual Property Law & Practice, vol. 9, no. 3, 2008, pp. 547–548.
1. D.M. German and A.E. Hassan, “License Integration Patterns: Addressing License Mismatches in Component-Based Development,” Proc. 31st Int'l Conf. Software Eng. (ICSE 09), IEEE CS, 2009, pp. 188–198.

Index Terms:
open source, copyright, licensing, provenance, legal compliance
Citation:
Daniel German, Massimiliano Di Penta, "A Method for Open Source License Compliance of Java Applications," IEEE Software, vol. 29, no. 3, pp. 58-63, May-June 2012, doi:10.1109/MS.2012.50
Usage of this product signifies your acceptance of the Terms of Use.