Difference between revisions of "Use Cases for EA-CoP Data Access and Sharing Policies"

Revision as of 23:11, 18 February 2013

Here follows a list of use cases for which the EA-CoP Data Access and Sharing Policies may apply.

Policy template

Strategy

The Strategy chapter positions the concerned Use Case in the broader context of iMarine objectives:

• Define the initiative and set the Goal
• Identify the benefits
• Position the role of the iMarine plaftform in respect of the concerned Use Case

Policy

The Policy chapter

• Define the properties/set of quality(*) required to achieve the specific objective
• Define the principles prevailing for the concerned use case; these principle refer to the general iMarine data sharing Policy (Disclaimer, Copyright, Posting Content, Shared Data, Public Data, Secondary Use, Derivative Work, and Data Citation) and might extend these
• Define the responsibilities of the various actors involved
• Define the type of collaborations required
• Define the kind of support required

Guidelines

The policy is extended with Guidelines:

• Metadata and models implementing the use case; this chapter includes a mapping with the business metadata
• Editorial workflow
• Roles and responsibilities in the workflow

(*) e.g. from FACP policy document: Objectivity; Reliability and timeliness; Length versus comprehensiveness; Hard copy – versus electronic format; Languages and translations; Partnerships

Code list management

content to be provided by Yann Laurent and Anton Ellenbroek, based on the various sub-use cases (FAO, Smartfish, FishFrame, DG MARE, eRS-FLUX)

iMarine Linked Open Data

content to be provided by Claudio Baldassare, Julien Barde, and Anton Ellenbroek

Strategy

The Strategy chapter positions LOD in the broader context of iMarine objectives:

• Define the initiative and set the Goal
  • a LOD network enabling to link database in scientifically accurate ways
  • Should be LOD in support to the EA; the name should try to reflect this (iMarineLOD, EA-LOD, ..., LODEA ???)

• Identify the benefits
  • Here we should be in a position to run demos on existing use cases (e.g. Smartfish, ) or explain them

• Position the role of the iMarine plaftform in respect of the LOD
  • iMarine is about scientific data on the EA
  • Harmonization, through code lists and their mapping, Code lists published as LOD, URIs integrated in scientific databases, which enables their linkage
  • iMarine helps in production and maintenance

Policy

The Policy chapter

• Define how to achieve the specific characteristic of LOD produced through iMarine
  • a LOD network enabling to link database in scientifically accurate ways
  • here I talked with Claudio of various “realms” of LOD, starting with a core (code lists and their mapping with a set of rules for access, attribution, provenance, quality, extending to a LOD periphery produced from controlled iMarine scientific databases (production of LOD from Geonetwork catalogs, or from Statistical databases), and finally to a third circle of LOD connections to external networks such as Agrovoc
• Define the principles under which
• Define the responsibilities of the various actors involved
• Define the type of collaborations
• Define the kind of support required

Guidelines

The policy will be extended with Guidelines:

• Metadata and models
• Editorial workflow
• Roles and responsibilities in the workflow

FAO Species fact sheet VREVirtual Research Environment. - App'lifish

Content to be input by Aureliano/Ellenbroek

Data provided through Web Services

Geospatial data and OGC Web-Services

• The geospatial data will be shared through OGC Web-Services (OWS)
  • Access to geospatial data as OGC WMSSee Workload Management System or Web Mapping Service./WFSWeb Feature Service/WCSWeb Coverage Service resources
  • Access to resources provided through ISO/IC211 - OGC metadata, served by CSW web-service with 2 access levels:
    • service metadata (ISO 19119:2005 / 19139) describing WxS instances specific to the data collection
    • dataset metadata (ISO 19115:2003 / 19139) describing each dataset
  • Such access could be completed later by Feature Catalogue description (ISO 19110), for data processing needs.
  • The set of metadata will be published in a CSW catalogue shared in i-Marine through Harvesting operation.
• A metadata constraints section will be added to the metadata, and will specify the license applicable to the data collection.
• Example: case of FAO aquatic species distributions, published through the FAO Geonetwork

Others

• ... to be input by Aureliano/Ellenbroek

Resources selector

Content to be provided by Ellenbroek

WIOFish

Content to be provided by Laurent