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) |
Marc.taconet (Talk | contribs) (→FAO Species fact sheet VRE - App'lifish) |
||
Line 20: | Line 20: | ||
*Secondary Use | *Secondary Use | ||
*Derivative Work and Data Citation | *Derivative Work and Data Citation | ||
+ | |||
+ | |||
+ | == Code list management == | ||
+ | |||
+ | |||
+ | == iMarine Linked Open Data == | ||
+ | |||
+ | The Strategy chapter would position LOD in the broader context of iMarine objectives: | ||
+ | - Define the initiative and set the Goal | ||
+ | o a LOD network enabling to link database in scientifically accurate ways | ||
+ | o Should be LOD in support to the EA – the name should try to reflect this (iMarineLOD, EA-LOD, ..., LODEA ???) | ||
+ | - Identify the benefits | ||
+ | o 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 | ||
+ | o iMarine is about scientific data on the EA | ||
+ | o Harmonization, through code lists and their mapping, Code lists published as LOD, URIs integrated in scientific databases, which enables their linkage | ||
+ | o iMarine helps in production and maintenance | ||
+ | |||
+ | The Policy would | ||
+ | - Define how to achieve the specific characteristic of LOD produced through iMarine | ||
+ | o a LOD network enabling to link database in scientifically accurate ways | ||
+ | o 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 | ||
+ | |||
+ | The policy will be extended with Guidelines: | ||
+ | - Metadata and models | ||
+ | - Editorial workflow | ||
+ | - Roles and responsibilities in the workflow | ||
+ | |||
+ | |||
Revision as of 22:43, 18 February 2013
Here follows a list of use cases for which the EA-CoP Data Access and Sharing Policies may apply.
Policy template
(from FACP policy document)
- Objectivity
- Reliability and timeliness
- Length versus comprehensiveness
- Hard copy – versus electronic format
- Languages and translations
- Partnerships
(from iMarine draft policy document)
- Disclaimer
- Copyright
- Posting Content
- Shared Data
- Public Data
- Secondary Use
- Derivative Work and Data Citation
Code list management
iMarine Linked Open Data
The Strategy chapter would position LOD in the broader context of iMarine objectives: - Define the initiative and set the Goal o a LOD network enabling to link database in scientifically accurate ways o Should be LOD in support to the EA – the name should try to reflect this (iMarineLOD, EA-LOD, ..., LODEA ???) - Identify the benefits o 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 o iMarine is about scientific data on the EA o Harmonization, through code lists and their mapping, Code lists published as LOD, URIs integrated in scientific databases, which enables their linkage o iMarine helps in production and maintenance
The Policy would - Define how to achieve the specific characteristic of LOD produced through iMarine o a LOD network enabling to link database in scientifically accurate ways o 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
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