SeaDataNet Ontology Use Case SeaDataNet Ontology Use Case Roy Lowry British Oceanographic Data Centre Coastal Atlas Interoperability Workshop, Corvallis, Coastal Atlas Interoperability Workshop, Corvallis, July 17-19 2007 July 17-19 2007 (+ Lessons Learned) (+ Lessons Learned)
SeaDataNet Ontology Use Case. Coastal Atlas Interoperability Workshop, Corvallis, July 17-19 2007. Roy Lowry British Oceanographic Data Centre. (+ Lessons Learned). Summary. What is SeaDataNet? Some SeaDataNet semantic issues What has SeaDataNet done? What is SeaDataNet going to do? - PowerPoint PPT Presentation
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
SeaDataNet Ontology Use Case SeaDataNet Ontology Use Case
Roy Lowry
British Oceanographic Data Centre
Coastal Atlas Interoperability Workshop, Corvallis, July 17-19 2007Coastal Atlas Interoperability Workshop, Corvallis, July 17-19 2007
(+ Lessons Learned)(+ Lessons Learned)
SummarySummary
What is SeaDataNet?
Some SeaDataNet semantic issues
What has SeaDataNet done?
What is SeaDataNet going to do?
Is SeaDataNet relevant to CAI?
What is SeaDataNet?What is SeaDataNet?
SeaDataNet in a Nutshell Combine over 40 oceanographic data centres across
Europe into a single interoperable data system
Approach is to adopt established standards and technologies wherever possible
Two phases:
One brings 12 centres together with centralised metadata and distributed data as files. Due fully operational in autumn 2008 (beta next February)
Two introduces data virtualisation, aggregation, cutting and 30 more centres. Due in 2010
Project is well on its way up the interoperability operational implementation curve
The major problem facing the project is heterogeneous legacy content SeaDataNet inherited 3 independently-developed
metadatabases
Each is heavily populated (3000-30000 records)
Each had its own independently developed controlled vocabularies
These vocabularies
– Covered overlapping domains
– Said similar things in different ways
– Provided a shining example of how NOT to manage vocabularies
Brief DiversionBrief Diversion
Vocabularies can have two types of governance Content governance
Mechanism for making decisions on vocabulary population– Expected deliverables include:
» Vocabulary standards and internal consistency» Change on a timescale matching the needs of
the user community» Terms with definitions!!!
Technical governance Vocabulary storage, maintenance and serving
– Expected deliverables include:» Convenient access to up to date vocabularies» Clear, rigorous vocabulary versioning» Version history through audit trails» Maintenance that doesn’t break user systems