CITADEL D6.4 Initial IPR Registry · Abstract: The IPR registry will be released in a first version at M12 and updated every year to include updated licenses of the final environment

D6.4 – Initial IPR Registry Version 1.0 – Final. Date: 30.09.2017

Project Title: CITADEL Contract No. GA 726755

www.citadel-h2020.eu

Page 1 of 18

Empowering Citizens to Transform European Public Administrations

Deliverable D6.4

Initial IPR Registry

Editor(s): Leire Orue-Echevarria Juncal Alonso

Responsible Partner: TECNALIA

Status-Version: Final – v1.0

Date: 30/09/2017

Distribution level (CO, PU): PU




Page 2 of 18

Project Number: GA 726755

Project Title: CITADEL

Title of Deliverable: Initial IPR Registry

Due Date of Delivery to the EC: 30/09/2017

Workpackage responsible for the Deliverable:

WP6 – Sustainability and Exploitation

Editor(s): Leire Orue-Echevarria (TECNALIA)

Contributor(s):

Leire Orue-Echevarria (TECNALIA) Marisa Escalante (TECNALIA) Juncal Alonso (TECNALIA) Gorka Benguria (TECNALIA) Iñaki Etxaniz (TECNALIA) Domenico Rotondi (FINCONS) Gayane Sedrakyan (IMEC)

Reviewer(s): Pieter Gryffroy (Time.Lex)

Approved by: All Partners

Recommended/mandatory readers:

All WP

Abstract: The IPR registry will be released in a first version at M12 and updated every year to include updated licenses of the final environment.

Keyword List: IPR registry, intellectual property rights

Licensing information: This work is licensed under Creative Commons Attribution-ShareAlike 3.0 Unported (CC BY-SA 3.0) http://creativecommons.org/licenses/by-sa/3.0/

Disclaimer This document reflects only the author’s views and neither Agency nor the Commission are responsible for any use that may be made of the information contained therein

http://creativecommons.org/licenses/by-sa/3.0/




Page 3 of 18

Document Description

Document Revision History

Version Date Modifications Introduced

Modification Reason Modified by

v0.1 24/10/2016 First ToC version Leire Orue-Echevarria (TECNALIA)

v0.2 15/05/2017 Integrated comments and suggestions received by consortium partners to the table of contents

Leire Orue-Echevarria (TECNALIA)

V0.3 19/07/2017 Integrated contributions from partners (TECNALIA and FINCONS)

Leire Orue-Echevarria (TECNALIA)

V0.4 15/09/2017 Integrated contributions from TECNALIA

Juncal Alonso (TECNALIA)

V1.0 18/09/2017 Review comments addressed Juncal Alonso (TECNALIA)




Page 4 of 18

Table of Contents

Table of Contents .......................................................................................................................... 4

List of Figures ................................................................................................................................ 4

List of Tables .................................................................................................................................. 4

Terms and abbreviations ............................................................................................................... 5

Executive Summary ....................................................................................................................... 6

1 Introduction .......................................................................................................................... 7

1.1 About this deliverable ................................................................................................... 7

1.2 Document structure ...................................................................................................... 7

2 CITADEL Deliverables and methodology IPR ......................................................................... 8

3 CITADEL Software IPR .......................................................................................................... 10

4 Conclusions ......................................................................................................................... 17

References ................................................................................................................................... 18

List of Figures

FIGURE 1. CITADEL DELIVERABLES IN THE CITADEL WEB PAGE. ............................................................... 8

List of Tables

TABLE 1. OPEN SOURCE MOST COMMON LICENSES ................................................................................ 10 TABLE 2. CITADEL SOFTWARE COMPONENTS IPR ANALYSIS TRACKING ..................................................... 13




Page 5 of 18

Terms and abbreviations

APL APACHE Public License

BSD Berkeley distribution license

CC Co-creation

EC European Commission

EPL Eclipse Public License

GPL GNU public License

IP Intellectual Property

IPR Intellectual Property Rights

LGPL Lesser GPL

MIT MIT

MPL Mozilla Public License

OS Open Source

OSS Open Source Software

PL Proprietary licenses

RO Research Only Licenses




Page 6 of 18

Executive Summary

In order to facilitate the market success of the innovative deliverables of CITADEL, Intellectual Property Rights (IPR) management will play an important role, especially in the reduction of the risks for the players involved, i.e. the CITADEL consortium partners and the European Commission.

This deliverable introduces the means selected in CITADEL for assessing the IPR with respect to the different assets to be produced and delivered in the context of the project, whether in the form of reports, methodologies or software components. These assets are going to be produced in the different WPs of the CITADEL project.

The current report differentiates the IPR management for the different deliverables depending on their nature (report, methodology and software), and provides the means to manage and tackle any potential conflicts.

The included software IPR table will be continuously updated and reported on every year, as long as the development of the components of the CITADEL ecosystem evolves.




Page 7 of 18

1 Introduction

The present document contains information on the IPR (intellectual property rights) of the different deliverables and components developed as part of CITADEL.

1.1 About this deliverable

This deliverable comprises the description of the deliverables, methodology and software components IPR that will be produced in the context of CITADEL project. D6.4 provides the means for an efficient and effective handling of IPR issues, including the IPR reporting and IPR conflict management. This deliverable provides explanations about the causes why some specific licenses have already been selected in the context of CITADEL.

1.2 Document structure

D6.4 comprises two main sections, one describing the IPR issues related to the CITADEL deliverables that are in the form of a report or methodology. The other one tackles the issues related to CITADEL deliverables that consist of or include software (prototypes).

Section 2 presents some of the relevant licenses available for documents and methodologies and describes the one selected for CITADEL deliverables, including the justification for this selection.

Section 3 introduces the possibilities for the licenses of the prototypes to be delivered in CITADEL. It also includes an explanation of the potential conflicts between licenses and the procedure established in the project to manage these conflicts. Finally, section 3 includes the first version of the analysis of the licenses of the components of the CITADEL ecosystem at this stage (M12). This analysis will be updated along with the evolution of the components development in the CITADEL ecosystem.




Page 8 of 18

2 CITADEL Deliverables and methodology IPR

In the context of CITADEL project, several deliverables in the form of reports are going to be delivered. These reports will be published on the web-page of the CITADEL action (www.citadel-h2020.eu), under the Deliverables tab (see Figure 1).

Figure 1. CITADEL deliverables in the CITADEL web page.

The reports which are accessible through the web page are licensed under cc-by-sa license.

The CreativeCommons license [1] is based on the Open Access movement, and allows the authors to keep their copyright allowing others to copy and distribute their work but under some specific conditions stated by the author in the license. The CreativeCommons license finds a middle ground between the standard “all rights reserved” (copyright license) and the public domain, i.e. “no rights reserved”.

For a work under a CreativeCommons license, the author can select a set of conditions he/she wants to have applied to his/her work:

Attribution (by): All CC licenses require that others who use a third party’s work in any way (copy, reproduce, distribute, communicate, traduce, adapt etc) and wants to make a commercial work with it, the original authors need to be cited and recognized.

Share alike (sa): The authors let others copy, distribute, display, perform, and modify they work as long as they distribute any modified work on the same terms. If they want to distribute modified works under other terms, they must get the authors’ permission first.

Non-commercial (nc): The authors let others copy, distribute, display, perform, and (unless Non-Derivatives condition is chosen) modify and use their work for any purpose other than commercially unless they get your permission first.

Non-derivatives (nd): The authors let others copy, distribute, display and perform only original copies of their work. If they want to modify the authors’ work, they must get the authors’ permission first.

http://www.citadel-h2020.eu/




Page 9 of 18

With this in mind, in the context of CITADEL, reports (textual deliverables and the co-creation methodology) are licensed under cc-by-sa. This license lets others remix, tweak, and build upon the authors work even for commercial purposes, as long as they credit the authors and license their new creations under the identical terms. This license is often compared to “copyleft” free and open source software licenses. All new works based on the authors’ will carry the same license, so any derivatives will also allow commercial use [2].

The CreativeCommons licenses provide several advantages [3]:

It provides global recognition and has international application, specifically designed to be global in their application, and to be enforceable with the same effect in any jurisdiction, protecting the authors, in this case, CITADEL partners from bad usage of the content delivered.

It supports community sharing, providing the possibility to disseminate us much as possible CITADEL deliverables, but always maintaining the attribution to the authors (CITADEL consortium).

It enables the content derived from the CITADEL project to be re-used by the community, increasing the impact reached.

It contributes to the open access movement (equivalent to the open source movement in the software), as mandated by the EC, increasing the throughput and collection of the results from other contributors.




Page 10 of 18

3 CITADEL Software IPR

The CITADEL project will deliver a set of software components, namely CITADEL ICT enablers, which will constitute the CITADEL ecosystem. This CITADEL ecosystem will be composed of different software components implemented by different technology partners in the consortium (FINCONS, imec, TECNALIA). At the same time, the different components developed by different partners, can be based on existing components which are modified, extended and customized for the CITADEL ecosystem.

The licensing of the CITADEL ecosystem components will be proposed by each component owner, taking into consideration that the CITADEL ecosystem should be offered as open source, following whenever possible a freemium licensing schema, where certain sophisticated features will not be offered as open, as stated in the DoA [4].

The open source part CITADEL Ecosystem will be available in an open Gitlab repository. As part of the open source strategy, the potential contribution of the CITADEL project to relevant open source projects will be evaluated.

As the CITADEL ecosystem will be composed of different software components with different licenses, which at the same time can be based on other existing tools, the technology partners need to be aware of the potential conflicts between the most common open source licenses.

In the next table, the conflicts of the most common open-source licenses [5] are presented, including the following information per license:

License name

License acronym

Danger: Estimation about the danger of using this type of license. This estimation has been made based on the knowledge and experience of the CITADEL partners.

Viral: The derivative works needs to be published compatible licenses.

Derivative: Derivations from the original work are allowed.

Allows commercial

Allows code closure

Conflictive: It presents conflicts when combining with other licenses.

Conflict: If it is a conflictive license, the conflict is specified here.

Table 1. Open source most common licenses

Common Licenses

Acronym Danger Viral Derivative works

Allows commercial

Allows code closure

Conflictive Conflict

APACHE Public License

APL MEDIUM NO Allowed YES YES YES Allegedly conflictive with GPL

Berkeley distribution license

BSD LOW NO Allowed YES YES NO None

GNU public License

GPL Very HIGH

YES Must be GPL

YES NO YES Incompatible with EPL, APL and others

Lesser GPL LGPL HIGH YES Must be YES NO YES Incompatible




Page 11 of 18

Common Licenses

Acronym Danger Viral Derivative works

Allows commercial

Allows code closure

Conflictive Conflict

*GPL with EPL, APL and others

Eclipse Public License

EPL HIGH PARTLY Must be EPL

YES NO YES Cannot incorporate source code from MPL, GPL, LGPL

Research Only Licenses

Very HIGH

NO Rarely allowed

NO N/A YES Usually you cannot incorporate anything

Proprietary licenses

Very HIGH

NO Rarely allowed

NO N/A YES Usually you cannot incorporate anything

Mozilla Public License

MPL HIGH PARTLY Must be MPL

YES NO YES Cannot incorporate source code from EPL, GPL, LGPL

MIT MIT LOW NO Allowed YES YES NO None

In order to assess if the sub-component (a component inside a CITADEL component) is in conflict due to the license of the basis software used in its implementation, the following procedure has been established:

1. No conflicts with respect to the licences: In this case the license for the subcomponent will be aligned with the CITADEL consortium decision about licenses (with the agreement of the partner responsible for the development of the component). This will be the case when any of the following situation occurs:

i. The sub-component owner has written the code totally from scratch ii. The sub-component contains new code and third party code licensed under

APL, BSD or MIT. iii. The sub-component contains source code licensed under EPL or MPL, but it is

not derivative from that code. It only co-distributes that code. The other remaining code complies with i or ii.

iv. The sub-component uses code licensed under GPL or LGPL but that code does not need to be co-distributed with the subcomponent (i.e it is a pre-requisite for installing the sub-component) even if that GPL licensed third party component is compiled on the user’s machine. The other remaining code complies with i, ii or iii.

2. If it represents any conflict because the sub-component must be licensed under a concrete license from the list:

i. MPL: The subcomponent must be licensed under MPL and no GPL or LGPL, proprietary or research only code can be introduced to the derived work and




Page 12 of 18

any included third party’s code under EPL license must be included in such a way that the sub-component is not considered derivative from the EPL code, only co-distributes it.

ii. EPL: The subcomponent must be licensed under EPL and no GPL or LGPL, proprietary or research only code can be introduced to the derived work and any included third party’s code under MPL license must be included in such a way that the sub-component is not considered derivative from the MPL code, only co-distributes it.

iii. LGPL: The subcomponent must be licensed under LGPL and it cannot include any APL, MPL, GPL, or EPL code.

iv. GPL: The subcomponent must be licensed under GPL and it cannot include any APL, MPL, or EPL code

v. RO (research-only): The subcomponent must be licensed under RO and no modifications can be made unless permitted under specific conditions in the licenses.

vi. Proprietary: The subcomponent must be licensed under proprietary and no modifications can be made unless permitted under specific conditions in the licenses and the partner owns a license to use and share the software in the project.

For the time being an initial registry of the components and subcomponents along with the relying tools has been performed (Table 2). This table will be accordingly updated every time a new version of a component in the ecosystem is released.

In this table, per each CITADEL ecosystem component the license is selected, as well as the sub-components dependencies with respect to IPR.




Page 13 of 18

Table 2. CITADEL software components IPR analysis tracking

Name of component

License if agreed

Partner / person responsible

Component license conflict

Third party subcomponent

Subcomponent owner/backer

Subcomponent license

Subcomponent license conflict?

Notes Technology

Stand alone

Last update

CP- ABE Service

FINCONS / Illuzzi

To be analysed

cpabe Junwei Wang GPL2 Java Javascript

No 21/06/17

Restlet Restlet S.A.S. Apache 2.0

CryptoJS Kenji Urushima

MIT

JSRSASign Kenji Urushima

MIT

jPBC Free Software Foundation, Inc.

GPL

BouncyCastle The Legion of the Bouncy Castle Inc.

MIT

Blockly Google Inc. Apache 2.0

AuthN / AUthZ

FINCONS / Illuzzi

To be analysed

W3C Web Crypto API

W3C® W3C SOFTWARE AND DOCUMENT NOTICE AND LICENSE

Java Javascript

No 21/06/17

CryptoJS Kenji Urushima

MIT

JSRSASign Kenji Urushima

MIT

jPBC Free Software Foundation, Inc.

GPL

BouncyCastle The Legion of the Bouncy Castle Inc.

MIT

https://github.com/junwei-wang/cpabe

http://opensource.org/licenses/apache-2.0






Page 14 of 18

Name of component

License if agreed







Notes Technology

Stand alone

Last update

Innovation Platform

FINCONS / Illuzzi

To be analysed

OpenideaL

Linnovate Techonologies.

GPL2 PHP Javascript

Yes 21/06/17

Drupal Drupal Association

GPL2

Digital Government Maturity Assessment Tool (DIGIMAT)

Proprietary with free use without charges

TECNALIA No No N/A N/A N/A Deployed on OpenStack at TECNALIA’s CloudLab

HTML5, Apache, MySQL

Yes 19/07/2017

No BIRT Eclipse Foundation

EPL No Java

Anonymization Engine

TECNALIA To be analysed

ARX API Fabian Prasser, Florian Kohlmayer and Contributors.

Apache License, Version 2.0

Java No 19/07/2017

User Assessement

To be decided


No 15/09/2017

Intelligent Discovery of public services

To be decided


No 15/09/2017

KPI report generation

To be decided

TECNALIA JHipster framework

JHipster Apache 2 To be analysed

Spring Boot and Angular

15/09/2016

BIRT Eclipse Foundation

EPL No




Page 15 of 18

Name of component

License if agreed







Notes Technology

Stand alone

Last update

Data Harvesting/Curation/Fusion

The Datatank is licenced under aGPLv3 Licence

IMEC To be analysed

No IMEC The RMLWorkbench is licenced under MIT Licence

N/A Most probably will be using a unified interface in Java/JSP/JS and the algorithms from subcomponents will be converted to use the same technologies

DataTank Framework: Laravel 4.2 (LTS) & open

sourceBack-end: PHP5.6+ (PHP7 compatible

)Front-end:

jQueryDatabase: MySQL (MariaDB)

Supported data sources: XLS, XML, RDF/XML, Turtle, SPARQL, Elasticsearch, SHP, CSV, JSON, JSON-LD, GeoJSON, RMLWorkbench –

Yes 15/09/2017




Page 16 of 18

Name of component

License if agreed







Notes Technology

Stand alone

Last update

Java, Node.js




Page 17 of 18

4 Conclusions

IPR management is a key aspect for research and innovation actions. It enables the development and maintenance of a schedule of innovation produced throughout the project lifetime.

This deliverable provides an explanation of the procedures and means implemented in CITADEL for the IPR reporting (both for software and report - based deliverables) and resolution of any issues related to the IPR management. Special attention has been paid to the analysis of potential conflicts between open source licenses in the context of the CITADEL ecosystem, as it will be composed of several components and subcomponents where the licenses need to be compatible.

The CITADEL software IPR table will be continuously updated and released every year to include updated licenses of the final environment.




Page 18 of 18

References

[1] Creative Commons, “Crative Commons,” [Online]. Available: https://stateof.creativecommons.org/. [Accessed 14 09 2017].

[2] Commons Creative, “CC licenses,” [Online]. Available: https://creativecommons.org/licenses/. [Accessed 14 09 2017].

[3] Creative Commons Australia, “what are the benefits of offering and using creative commons licences?,” Creative Commons.

[4] CITADEL consortium, “CITADEL DoA,” 2016.

[5] Open source project, “Open source,” [Online]. Available: https://opensource.org/licenses. [Accessed 14 09 2017].

Documents

CITADEL D6.4 Initial IPR Registry · Abstract: The IPR registry will be released in a first version at M12 and updated every year to include updated licenses of the final environment