Roy Lowry Adam Leadbetter British Oceanographic Data Centre.

Slides:



Advertisements
Similar presentations
LRI Validation Suite Meeting August 16, Agenda Review of LRI Validation Suite Charter/Overview Acquiring test data update Review of proposed test.
Advertisements

Status of vocabulary developments Roy Lowry, Adam Leadbetter, Rob Thomas & Ray Cramer SDN TTG & EMODnet Chemistry 2 TWG – Trieste, Italy.
A Semantic Modelling Approach to Biological Parameter Interoperability Roy Lowry & Laura Bird British Oceanographic Data Centre Pieter Haaring RIKZ, Rijkswaterstaat,
The BODC Parameter Markup and Usage Vocabulary Semantic Model Roy Lowry British Oceanographic Data Centre GO-ESSP Meeting, RAL, June 2005.
Vocabulary management: a foundation for semantic interoperability through ontology development Roy Lowry British Oceanographic Data Centre GO-ESSP, Paris,
NERC DataGrid Vocabulary Governance Vocabulary Workshop, RAL, February 25, 2009.
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
1 Review.  Influences  Problem Domain  Ilities  Marketecture and Tarchitecture Collide  Technology Base  Human Influences on This  Results now.
Demonstration of adding content to an ICAN Semantic Resource Roy Lowry, Adam Leadbetter, Olly Clements (NETMAR - BODC) Tanya Haddad (ICAN - OCA)
XML, DITA and Content Repurposing By France Baril.
The NERC DataGrid Vocabulary Server Roy Lowry British Oceanographic Data Centre Ontology Registry Meeting.
The NERC DataGrid Vocabulary Server: an operational system with distributed ontology potential Roy Lowry British Oceanographic Data Centre GO-ESSP 2008,
SeaDataNet Ontology Use Case Roy Lowry British Oceanographic Data Centre Coastal Atlas Interoperability Workshop, Corvallis, July (+ Lessons.
Status of upgrading CDI service (user interface, harvesting via GeoNetwork, CDI interoperability options following SeaDataNet D8.7) By Dick M.A. Schaap.
MEDIN Data Guidelines. Data Guidelines Documents with tables and Excel versions of tables which are organised on a thematic basis which consider the actual.
Marine Data Management within EMODNet Chemistry project: data aggregation, quality control and products preparation A.S. Iona 1, P. Karagevrekis 1, S.Balopoulou.
EMODNET Chemistry 2 Steering Group Rome (Italy), January 2014 WP 1 : DATA COLLECTION AND METADATA COMPILATION IN ATLANTIC SEA.
Controlled Vocabularies (Term Lists). Controlled Vocabs Literally - A list of terms to choose from Aim is to promote the use of common vocabularies so.
SeaDataNet2 Plenary meeting, 19th-20th September 2012, Rhodes SeaDataNet2 Plenary meeting THE EMODNET CHEMISTRY LOT. FROM THE EXPERIENCE OF THE THREE YEARS.
Workshop – 10, December 2014, Berlin ICCS / NTUA Greece Efthymios Chondrogiannis An Intelligent Ontology Alignment Tool Dealing with Complicated Mismatches.
Integrating and managing your Engaging Networks data Top ten data features.
ECHO DEPository Project: Highlight on tools & emerging issues The ECHO DEPository Project is a 3-year digital preservation research and development project.
From Emodnet Chemical Pilot to Emodnet Chemistry 2 Matteo Vinci, Istituto Nazionale di Oceanografia e di Geofisica Sperimentale – OGS – NODC group, Dipartimento.
NERC DataGrid Vocabulary Server Access Vocabulary Workshop, RAL, February 25, 2009.
Lecture 7 Integrity & Veracity UFCE8K-15-M: Data Management.
OpenURL Link Resolvers 101
EMODNET Chemistry 2 Semantic Suggestions Roy Lowry and Adam Leadbetter British Oceanographic Data Centre.
Expert Workshop, June , Split, Croatia Output from TG Data for MSFD implementation EMODnet Chemistry Giordano Giorgi - ISPRA.
IBM Software Group ® Overview of SA and RSA Integration John Jessup June 1, 2012 Slides from Kevin Cornell December 2008 Have been reused in this presentation.
NERC DataGrid NERC DataGrid Vocabulary Server Use Cases Vocabulary Workshop, RAL, February 25, 2009.
EMODnet Chemistry 2 Service Contract MARE/2012/10 S Progress of the CDI service By Dick M.A. Schaap – Technical Coordinator Istanbul – Turkey,
CDI Controlled Vocabularies Roy Lowry, Karen Vickers (BODC) Michele Fichaut, Catherine Maillard (SISMER) Reinhard Schwabe (DOD) 4 June 2003.
Annual Meeting, June , Istanbul, Turkey WP1: Data collection and metadata compilation in sea regions: current status EMODnet Chemistry Partner.
9 onshore monitored monthly 8 offshore monitored seasonally (2x/year – Spring & Autumn) EMODnet Chemistry 17 Stations.
Presenter: Nick Dalton Manager, e-Business Services MINISTRY OF ECONOMIC DEVELOPMENT REPORTING TO THE NEW ZEALAND COMPANIES OFFICE USING XBRL.
Annual Meeting, June , Istanbul, Turkey WP1: Data collection and metadata compilation in sea regions: current status EMODnet Chemistry Partner.
TDWG Life Sciences Identifiers Applicability Statement Ben Richardson Review Manager, LSID Applicability Statement Western Australian Herbarium Department.
HNDIT23082 Lecture 06:Software Maintenance. Reasons for changes Errors in the existing system Changes in requirements Technological advances Legislation.
EMODnet Chemistry 2 Service Contract MARE/2012/10 S How to make EMODnet Chemistry fit for purpose at system level By Dick M.A. Schaap – Technical.
Annual Meeting, June , Istanbul, Turkey WP1: Data collection and metadata compilation in sea regions: current status EMODnet Chemistry Partner.
LRI Validation Suite Meeting Prototype Tool Demonstration December 20th, 2011.
EMODNet Chemistry (MARE/2012/10). The portal should collect the following groups of chemicals: - in 3 matrices: water column, biota, sediment. - in all.
The Akoma Ntoso Naming Convention Fabio Vitali University of Bologna.
Download Manager software Training Workshop Ostend, Belgium, 20 th May 2014 D.M.A. Schaap - Technical Coordinator.
Roy Lowry British Oceanographic Data Centre.  Controlled Vocabularies - What and Why  Controlled Vocabularies - History  Controlled Vocabularies -
3rd Training Workshop June 2008, Ostende Management of CSR Anne Che-Bohnenstengel, BSH  Metadata Formats  Defined Vocabularies  Content Management.
© 2010 IBM Corporation RESTFul Service Modelling in Rational Software Architect April, 2011.
WP3 - Quality Control survey findings and gaps M. Vinci, A. Giorgetti.
EMODnet Chemistry 2 Service Contract MARE/2012/10 S Progress of the CDI service By Dick M.A. Schaap – Technical Coordinator Helsinki – Finland,
Annual Meeting, June , Istanbul, Turkey WP1: Data collection and metadata compilation in sea regions: current status EMODnet Chemistry Partner.
DATA AGGREGATION AND PRODUCTS GENERATION
SeaDataNet tools NEMO, OCTOPUS, MIKADO
P01 parameters: tips and tools
Usage of BODC parameter vocabularies
ODV format templates for nutrients, dissolved gases and contaminants in different matrixes (water, sediment, biota) OGS – Marina Lipizer EMODnet Chemistry.
Data aggregation and products generation in the Mediterranean Sea
WP3: Data validation and MSFD interaction
A Metadata System for Geomagnetism
Active Data Management in Space 20m DG
Vanessa Tosello (IFREMER), Flavian Gheorghe (MARIS)
Vocabularies at the British Oceanographic Data Centre
EMODnet Chemistry WP1: Data collection and metadata compilation in sea regions: current status Partner 40: State Oceanographic Institute Alexander Korshenko,
WebDAV Design Overview
EMODnet Chemistry WP1: Data collection and metadata compilation in sea regions: current status Partner contribution: BODC Annual Meeting, June ,
Lecture 06:Software Maintenance
EMODnet Chemistry WP1: Data collection and metadata compilation in sea regions: current status Partner contribution: ISPRA Annual Meeting, June ,
EMODnet Chemistry WP1: Data collection and metadata compilation in sea regions: current status Partner contribution: Latvian Institute of Aquatic Ecology.
ONTOMERGE Ontology translations by merging ontologies Paper: Ontology Translation on the Semantic Web by Dejing Dou, Drew McDermott and Peishen Qi 2003.
2018 Freshwater data call Stéphane Isoard
EMODnet Chemistry 3 Generation of data products in the Baltic Sea
Presentation transcript:

Roy Lowry Adam Leadbetter British Oceanographic Data Centre

Overview Automated parameter aggregation (P35) vocabulary status EMODNET chemical filter P01 semantic model exposure status Management of concept deprecations

P35 Status P35 is a vocabulary of parameters for EMODNET chemistry lot products EMODNET data parameters are marked up using P01 vocabulary P01 is much finer grained than P35 Therefore aggregation of P01 parameters into P35 parameters is required To date this has been done by a lot of painful manual work in ODV

P35 Status However within NVS it is possible to maintain and serve a mapping between P01 and P35 Each P35 concept has a URL that resolves to an XML document This document can be used to drive automated parameter aggregation by identifying all P01 codes that may be incorporated into a P35 code

P35 Status P35 presents design issues P35 granularity (e.g. should there be separate products for unfiltered and filtered samples) Which P01 terms should map to a given P35 term? Design issues need governance - domain experts who can make these decisions Governance now established based on experts from EMODNET partners communicating by list-server e- mail and Webex.

P35 Status Example P35 concept (ITS90 temperature) set up in October Just over 100 additional entries considered by governance and loaded this month These cover Salinity Dissolved oxygen Nutrients Metals in the water column Next target is metals in sediments and biota ( ) P35 could easily reach several thousand entries

EMODNET Chemical Filter Need to consider what is required here One approach is to specify a list of P02 codes that cover the themes included in the EU legislation This comes with risks Some data outside the intended scope will be captured (e.g. Methylated arsenic in a trawl designed for organotins) Easy to overlook consequences of any P02 rationalisation P02 list can be tested against P35 (both map to P01)

EMODNET Chemical Filter Alternative approach Capture P01 codes through data mining Translate P35 into a list of P01 codes Do the chemical filter on the basis of P01 rather than P02

P01 Model Exposure Status Both ODIP and EMODNET require access to the factored semantic model that underpins P01 Strong pressure from ODIP (primarily Simon Cox) for this to be delivered through RDF-XML For this every element of the factorisation requires a URI This requires that every element to be covered by a controlled vocabulary

P01 Model Exposure Status The biological entity in the factorisation is already covered (S25 vocabulary) Parameter - matrix relationship already covered (S02 vocabulary) Currently working on the matrix entity Concepts like 'water body particulate >0.2um phase' Taking longer than expected (part-time working, EMODNET, IMOS vocabulary demands, past misdemeanours) But getting very close Then we just need the parameter entity

Concept Deprecation Many SeaDataNet vocabularies have evolved, with concepts added to satisfy specific demands Governance explicitly prohibits deletion This leads to issues Unintended duplicates Cause confusion Unnecessarily complicate aggregation Variable granularity Discovery made more difficult (too many terms) Patchy domain coverage Unnecessarily complicates metadata markup

Concept Deprecation NVS 1.0 handled deprecation poorly (URI changed) Issues addressed in NVS 2.0 All payload documents include skos:note element set to 'accepted' or 'deprecated' owl:deprecated boolean element Deprecated concept documents also have a dc:isReplaced By element Full controlled vocabulary requests may be designated 'accepted', 'deprecated' or 'all' (default)

Concept Deprecation Concept deprecation causes issues for the SeaDataNet architecture Deprecated concepts contained in SeaDataNet metadatabases Deprecated concepts in SeaDataNet filestock Consequently, much needed vocabulary improvements (P03, P02) held back due to concern about the consequences

Concept Deprecation Following deprecation support is needed: Deprecation handling within the SeaDataNet vocabulary client, which could either Only display accepted concepts (easy to implement) Flag the deprecated concepts (more work but a better result) Automatic parameter substitution in metadatabase file and data file import tools Metadatabase sweepers (run regularly to clean up any concepts that have been deprecated since ingestion)