Maximising
Value
Minimising
Costs

Dr. Prodromos Tsiavos
EKT/ NHRF

Luxembourg
25.11.13
Monday, 25 November 2013

@prodrom...
0
Monday, 25 November 2013
open
licensing
is not the
same as
re-use
licesning
Monday, 25 November 2013
UNDERSTAND THE
DIFFERENCE

[ 0.1 ]

Re-Use licensing:
- may be open or not
- it may operate in parallel to
open licensing ...
APIs ToS

[ 0.2 ]

Monday, 25 November 2013

APIs ToS
(Terms of Service for APIs):
- they include re-use/ open
licensing
-...
1
Monday, 25 November 2013
DO NOT USE
LICENCES!

Monday, 25 November 2013
What the
Directive
Allows
Art. 8(1)

[ 1.1 ]

Monday, 25 November 2013

“Public sector bodies may
allow re-use without
con...
Features
Art. 8

[ 1.2 ]

* Introduce a provisional “PSI
as PD” regime
* Introduce Smart Notices
- permanent position
- ve...
Monday, 25 November 2013
2
Monday, 25 November 2013
DO NOT
REINVENT
THE WHEEL

Monday, 25 November 2013
USE
STANDARD
PUBLIC
LICENCES

Monday, 25 November 2013
Monday, 25 November 2013
REDUCE
RESTRICTIONS
IN THE
MINIMUM

[ 2 ]

Monday, 25 November 2013

- Use CC Zero
- Alternatively use CC BY
Avoid:
- NonC...
3
Monday, 25 November 2013
IF YOU CREATE AN
OGL
ENSURE
INTEROPERABILITY

Monday, 25 November 2013
EU Open Licensing Framework Model (current
situation)
MS1
User1

User2

EC

OGL1
EUOGL2

User3

CC/OKF
MS2

User4

* the E...
EU Open Licensing Framework Model
(single)
MS1
User2

EC

User1

User3
EUOGL or CC/ OKF

MS2

* single standard licence (e...
EU Open Licensing Framework Model
(standard)
MS1

OGL1

EC
OGL2
CC/OKF
MS2

* licensing coordination/ standardisation take...
FAIR LICENSING

- Store licences at a permanent
location
- Publicly announce revisions

[ 3.1 ]

Monday, 25 November 2013
...
DO NOT
MIX RIGHTS

[ 3.2 ]

- Do not add a personal data
licence clause
* use “smart notices” instead
- Resolve the Cultur...
GRANT STANDARD
RIGHTS

[ 3.3 ]

Monday, 25 November 2013

- Copyright
- Related/ Neighbouring
Rights
- Sui Generis Right
-...
USE STANDARD
RESTRICTIONS

[ 3.4 ]

- Attribution
* author
* designated person
(information provider/ owner/
funder etc)
*...
EXPLICATE
INTEROPERABILITY

[ 3.5 ]

Monday, 25 November 2013

- Be explicit about
interoperability:
* Versioning interope...
DO NOT USE A
PERSONAL DATA
CLAUSE

[ 3.6 ]

Monday, 25 November 2013

- Use Smart Notices Instead
* permanent location
* i...
A Scenario of Re-Use Licensing for Personal Data

ReUser1

PSB

ReUse
Agreement

EndUser1

Personal Data
Policy
EndUser2
R...
A Scenario of Open Data Licensing for Personal Data

ReUser1

PSB

OpenGov
Licence

ReUser3
ReUser6

ReUser4

Standard
Ope...
DO NOT ALLOW
RETROSPECTIVE
WITHDRAWAL

[ 3.7 ]

Monday, 25 November 2013

- licence termination should
not be retroactive
...
#conclusions

Monday, 25 November 2013
#1 PSI open by default
by law and design
#2 use standard
licences
#3 use minimal
conditions/
restrictions
#standardise API...
Q
#psiconsultation

Monday, 25 November 2013

+

A
tsiavos@ekt.gr
Upcoming SlideShare
Loading in …5
×

Open data licences interoperability_echearing_25_11_13pdf

479 views
408 views

Published on

This is the presentation I have given for the implementation of the 2013 PSI Directive focusing on the issue of Licence Interoperability and the need for a positive Public Domain right for Public Sector Information. It explores interoperability of Open Government Licences with Creative Commons and other standard public licences. I have given this presentation on behalf of the National Documentation Center/ National Hellenic Research Foundation and the Legal Aspects of Public Sector Information 2.0 Network.

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
479
On SlideShare
0
From Embeds
0
Number of Embeds
38
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Open data licences interoperability_echearing_25_11_13pdf

  1. 1. Maximising Value Minimising Costs Dr. Prodromos Tsiavos EKT/ NHRF Luxembourg 25.11.13 Monday, 25 November 2013 @prodromos #ekt.gr #PSI #opendata EC PSI Licensing Hearing SI P on ns tio ing es s lity gg cen u li bi S 3 era op te r in
  2. 2. 0 Monday, 25 November 2013
  3. 3. open licensing is not the same as re-use licesning Monday, 25 November 2013
  4. 4. UNDERSTAND THE DIFFERENCE [ 0.1 ] Re-Use licensing: - may be open or not - it may operate in parallel to open licensing (with an SLA) - the license issuer is normally the licensor as well - it increasingly makes use of APIs Open Licensing - is a form of re-use licensing - makes use of standard licences - requires minimum transaction costs and maximum interoperability Monday, 25 November 2013
  5. 5. APIs ToS [ 0.2 ] Monday, 25 November 2013 APIs ToS (Terms of Service for APIs): - they include re-use/ open licensing - they need to be standardised and transparent - they need to differentiate the ToS from the content licensing part - they need to also not unnecessarily restrict the PSI re-use - they may contain Service Level Agreements that also need to be transparent
  6. 6. 1 Monday, 25 November 2013
  7. 7. DO NOT USE LICENCES! Monday, 25 November 2013
  8. 8. What the Directive Allows Art. 8(1) [ 1.1 ] Monday, 25 November 2013 “Public sector bodies may allow re-use without conditions or may impose conditions, where appropriate through a licence. These conditions shall not unnecessarily restrict possibilities for re-use and shall not be used to restrict competition.”
  9. 9. Features Art. 8 [ 1.2 ] * Introduce a provisional “PSI as PD” regime * Introduce Smart Notices - permanent position - versioning - attribution * Registry for copyrighted PSI - re-used - open Monday, 25 November 2013
  10. 10. Monday, 25 November 2013
  11. 11. 2 Monday, 25 November 2013
  12. 12. DO NOT REINVENT THE WHEEL Monday, 25 November 2013
  13. 13. USE STANDARD PUBLIC LICENCES Monday, 25 November 2013
  14. 14. Monday, 25 November 2013
  15. 15. REDUCE RESTRICTIONS IN THE MINIMUM [ 2 ] Monday, 25 November 2013 - Use CC Zero - Alternatively use CC BY Avoid: - NonCommercial (definition issues) - Copyleft (ShareAlike) (compatibility issue) - NoDerivatives (not really open) - NoRedistribution (not really open)
  16. 16. 3 Monday, 25 November 2013
  17. 17. IF YOU CREATE AN OGL ENSURE INTEROPERABILITY Monday, 25 November 2013
  18. 18. EU Open Licensing Framework Model (current situation) MS1 User1 User2 EC OGL1 EUOGL2 User3 CC/OKF MS2 User4 * the EC introduces a single EC licence * the MS only use their own licences * Users use all EC, MS and Open Public Licences Monday, 25 November 2013 ECOL
  19. 19. EU Open Licensing Framework Model (single) MS1 User2 EC User1 User3 EUOGL or CC/ OKF MS2 * single standard licence (e.g. CC is used) Monday, 25 November 2013 User4
  20. 20. EU Open Licensing Framework Model (standard) MS1 OGL1 EC OGL2 CC/OKF MS2 * licensing coordination/ standardisation takes place in two steps: - EC coordinate and observes licensing standards between MS - MS standardise PSBs within their jurisdictions * the two standardisation processes take place in parallel Monday, 25 November 2013 EUOLS OGL: Open Gov Licence CC: Creative Commons Public Licence OKF: OKF Licence EUOL: EU Open Licence EUOLS: EU Open Licence Standard MS: Member State
  21. 21. FAIR LICENSING - Store licences at a permanent location - Publicly announce revisions [ 3.1 ] Monday, 25 November 2013 - Version licences
  22. 22. DO NOT MIX RIGHTS [ 3.2 ] - Do not add a personal data licence clause * use “smart notices” instead - Resolve the Cultural Heritage Right at the legislative level - Do not exclude Personal Data from the licensing Regime Monday, 25 November 2013
  23. 23. GRANT STANDARD RIGHTS [ 3.3 ] Monday, 25 November 2013 - Copyright - Related/ Neighbouring Rights - Sui Generis Right - Do not contractually limit PD/ Exemptions AND Fair Use/ Fair Dealing/ limitations/ exceptions
  24. 24. USE STANDARD RESTRICTIONS [ 3.4 ] - Attribution * author * designated person (information provider/ owner/ funder etc) * retain: >notices >licence (URI) >warranties >URI to the material * include preferred way of attribution - No sub-licensing - No Endorsement - Indicate this is a modified version Monday, 25 November 2013
  25. 25. EXPLICATE INTEROPERABILITY [ 3.5 ] Monday, 25 November 2013 - Be explicit about interoperability: * Versioning interoperability * Open Standard (Public) licences interoperability
  26. 26. DO NOT USE A PERSONAL DATA CLAUSE [ 3.6 ] Monday, 25 November 2013 - Use Smart Notices Instead * permanent location * indicate that the data set includes personal data * indicate the purpose of the original processing * no re-identification in the case of anonymised data
  27. 27. A Scenario of Re-Use Licensing for Personal Data ReUser1 PSB ReUse Agreement EndUser1 Personal Data Policy EndUser2 ReUser2 EndUser3 Combined Policies & End User Licence Agreement * The licences flow from the PSB to the original Re-users that then sublicense or provide Terms of Service to the End Users * The data protection policies/ terms of processing flow with the original licences to the Re-users and then as incorporated in the EULAs/ ToS to the End-Users. Monday, 25 November 2013 ReUser1
  28. 28. A Scenario of Open Data Licensing for Personal Data ReUser1 PSB OpenGov Licence ReUser3 ReUser6 ReUser4 Standard Open Licences ReUser6 ReUser2 ReUser5 Personal Data Processing Notice * The licences flow from the PSB to all Re-Users as well between Re-users. * Different standard licences are used to remix data * There is a Personal Data Processing Notice issued by the PSB and all Re-users have to point at it. Monday, 25 November 2013 ReUser1
  29. 29. DO NOT ALLOW RETROSPECTIVE WITHDRAWAL [ 3.7 ] Monday, 25 November 2013 - licence termination should not be retroactive - have a clearly defined termination process
  30. 30. #conclusions Monday, 25 November 2013
  31. 31. #1 PSI open by default by law and design #2 use standard licences #3 use minimal conditions/ restrictions #standardise API ToS/ SLAs Monday, 25 November 2013
  32. 32. Q #psiconsultation Monday, 25 November 2013 + A tsiavos@ekt.gr

×