Agroknow presentation of the current analysis of the legal interoperability in the fishery and marine sciences domain. The presentation was made in the EGI ENGAGE workshop, organised by the FAO Fisheries and Aquaculture Department.
2. 23/17/2016
• Who we are
• FAO Data Sharing Policy
• The case of FAO AGRIS data licensing
• Developing the legal interoperability of
data sharing within the fishery and marine
sciences
What you are going to see
6. 63/17/2016
Broader Legal Interoperability Landscape
We work at each project separately, focusing on the
needs and at the Vision that the institution wants to
express.
Each project for us is a commitment that serves people.
Meet the experts
But how we do that?
7. 73/17/2016
Broader Legal Interoperability Landscape
We are a team of experts, flexible,
intuitional that delivers
Expert in strategy
design
Expert in data and
technology solutions
Expert in customer
needs identification
and analysis
The Strategist The Doer The Perfectionist
Nikos Manouselis Giannis Stoitsis Babis Thanopoulos
but its not only the 3 of us
11. 113/17/2016
Broader Legal Interoperability Landscape
Supporting a large network of data
providers: the case of FAO AGRIS
• >180 organizations
• a data customer workflow and front end
• use of CRM for the network management
• interoperable and open architecture
19. 193/17/2016
Broader Legal Interoperability Landscape
Development of the Open Access & Data
Management Plan in alignment with the
CGIAR Open Access Policy Mandate
• Openness
• Suitable repositories
• Interoperability
• Data storage and preservation for future use
• Copyright and open licenses
24. 243/17/2016
The issues?
1. Hard to read the fine print / legal terms
used
2. Lack of use of existing standard licensing
schemes
3. Not machine-readable
4. Many FAO data sources point to this page
but licensing may need refinement for
various types of data
– Metadata, actual data, KOS, multimedia files
Broader Legal Interoperability Landscape
25. 253/17/2016
The Creative Commons example
• Legal Code - Each license begins as a traditional
legal tool, in the kind of language and text formats
that most lawyers know and love. This is the actual
license, which is a detailed legal document.
• Commons Deed - This is a handy reference that
summarizes and expresses some of the most
important terms and conditions. Think of the
Commons Deed as a user-friendly interface to the
Legal Code beneath, although the Deed itself is not
a license, and its contents are not part of the Legal
Code itself.
• Machine-readable version - The final layer of the
license design is a “machine-readable” version of
the license - a summary of the key freedoms and
obligations written into a format that software
systems, search engines, and other kinds of
technology can understand.
Broader Legal Interoperability Landscape
31. 313/17/2016
Including all dimensions
• Provision of various types of data shared
– Personal information
– Institutional information
– Collection information
– Cookies
– Other?
• To be covered in the updated FAO AGRIS data
policy (version 2 - in 2016)
Broader Legal Interoperability Landscape
33. 333/17/2016
Issues identified
• Hard to find data policies / licensing
• Data Policy / licensing not available
• High heterogeneity of existing licenses
– Important issue for legal interoperability
• Licensing not included in metadata
– Licensing information is lost during (metadata)
interoperability
Broader Legal Interoperability Landscape
34. 343/17/2016
Licensing used in the marine & fishery
context
Copyright &
other
Restrictions
Cuses of this
resource
allowed? (Y/N)
Modifications of your work
of this resource allowed?
(Y/N/share alike)
Cost (Y/N)
IODE N N Y N
NOAA / NCEI Centers N To be defined To be defined N
SeaDataNet N To be defined To be defined N
OBIS N Depends Y N
MGDS N Depends ShareAlike N
MEDIN Depends Depends Depends Depends
ICES Y N N N
AIMS N Y N N
GBIF N Depends Y N
ASFIS (FAO) N N Y N
Eurostat Depends Depends Y N
Broader Legal Interoperability Landscape
35. 353/17/2016
Multiple dimensions of legal
interoperability
Data ownership
(data producers)
• Do data producers
maintain
ownership?
• Will data producers
be credited?
• Is data properly
licensed?
• Are data producers
properly informed?
Broader Legal Interoperability Landscape
Data access
(data users)
• Is access to data
open (or registration
needed)?
• Is access to data
free?
• Is there provision for
technical
interoperability?
• Is there provision for
legal interoperability
Data use
(data consumers)
• Are modifications
allowed?
– Translations
– Summaries
– Application of text
mining
• Are commercial
uses allowed?
• Is ShareAlike a
requirement?
36. 363/17/2016
Initial steps on the
legal interoperability of
data sharing within the fishery
and marine sciences
Broader Legal Interoperability Landscape
37. 373/17/2016
Use of standards
• 6 out of 13 data marine/fisheries data
sources examined adopted CC licenses
• Copyrighted material exists in several cases
• Licensing is not always available
• Licensing is not always clear / optimum
Broader Legal Interoperability Landscape
38. 383/17/2016
Recommendations / next steps (1/2)
• Use of existing licensing standards needs to be
considered and adapted by data providers
• Existing licensing schemas to be mapped to
such standards
• Machine readable formats expected to increase
reuse and value of data
– Openly licensed data get more credits by researchers
• Various types of stakeholders need to be
consulted
– Researchers, legal experts, domain experts, repository
managers, etc.)
Broader Legal Interoperability Landscape
39. 393/17/2016
Recommendations / next steps (2/2)
• Creative Commons is not the only way to go (but
looks like a great one)
• The UNESCO/IOC Oceanographic Data Exchange
Policy has the potential to be adapted globally
(www.iode.org/policy)
• Data providers need to be educated on the
importance of licensing (and open data)
Broader Legal Interoperability Landscape
The machine-readable code can be obtained using the CC license chooser tool. Once a license is identified, the tool automatically generates the HTML syntax which can be copied and embedded into web pages on the Internet. This syntax would not be visible to people browsing your web pages but can be read by search engines and in this sense, CC licenses are "machine-readable".