Difference between revisions of "Use Cases for EA-CoP Data Access and Sharing Policies"
Marc.taconet (Talk | contribs) (→FAO Species fact sheet VRE - App'lifish) |
(→iMarine Linked Open Data) |
||
Line 30: | Line 30: | ||
content to be provided by Yann Laurent and Anton Ellenbroek, based on the various sub-use cases (FAO, Smartfish, FishFrame, DG MARE, eRS-FLUX) | 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 == | + | == iMarine EA Linked Open Data Initiative== |
− | content to be provided by Claudio | + | content to be provided by Claudio Baldassarre, Julien Barde, and Anton Ellenbroek |
=== Strategy === | === Strategy === | ||
Line 38: | Line 38: | ||
* Define the initiative and set the Goal | * Define the initiative and set the Goal | ||
− | + | The EA-iMarine-LOD, initiative promoted by FAO, is meant to develop the necessary capacities in the infrastructure, to instantiate a network of interlinked datasets of scientifically accurate data in the domain of EA to fisheries. The EA-iMarine-LOD is contributed in portions by the partners willing to be part in return of mutual data enrichment. Such distributed evolution paradigm fits well with the structure of network of interlinked datasets. | |
− | + | ||
+ | The goal of this initiative is to supply what providers lack: the resources, the technical expertise, or when they can’t find the proper tools. In doing so the initiative will set a plan of development for LOD engineering tools built on data access facilities. Innerly the goal of this initiative is to help to overcame the challenges of LOD engineering that is demanding and requires actions beyond the simple creation of datasets ( e.g. complex ETL workflows, and to be bound to full dataset lifecycle) | ||
* Identify the benefits | * Identify the benefits |
Revision as of 18:12, 7 March 2013
Here follows a list of use cases for which the EA-CoP Data Access and Sharing Policies may apply.
Template for the Policy use cases
Strategy
The Strategy chapter positions the concerned Use Case in the broader context of iMarine objectives (draw a link to relevant Wiki page in case the strategy has already been defined elsewhere):
- 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 EA Linked Open Data Initiative
content to be provided by Claudio Baldassarre, 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
The EA-iMarine-LOD, initiative promoted by FAO, is meant to develop the necessary capacities in the infrastructure, to instantiate a network of interlinked datasets of scientifically accurate data in the domain of EA to fisheries. The EA-iMarine-LOD is contributed in portions by the partners willing to be part in return of mutual data enrichment. Such distributed evolution paradigm fits well with the structure of network of interlinked datasets.
The goal of this initiative is to supply what providers lack: the resources, the technical expertise, or when they can’t find the proper tools. In doing so the initiative will set a plan of development for LOD engineering tools built on data access facilities. Innerly the goal of this initiative is to help to overcame the challenges of LOD engineering that is demanding and requires actions beyond the simple creation of datasets ( e.g. complex ETL workflows, and to be bound to full dataset lifecycle)
- 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 prevailing for the implementation of LOD
- 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
Taxonomic data
the WORMS use case
Policy to stem from the MoU to be elaborated between iMarine and VLIZ
Sharing taxonomic data
Edward VandenBerg and Nicolas Bailly as part of Edward's TORs
FAO Species fact sheet VREVirtual Research Environment. - App'lifish
Content to be input by Aureliano/Ellenbroek
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
SmartFish
Content to be provided by Laurent