Top Level Ontology

From D4Science Wiki
Revision as of 11:05, 3 July 2013 by Carlo.allocca (Talk | contribs) (→‎TCOM in Greece, Skiathos, 18.06.2013 (LATEST))

Jump to: navigation, search

Latest (June 2013) slide presentation

Person responsible for editing/maintaining this page

  • Carlo Allocca
  • e-mail: carlo@ics.forth.gr

TLO-Development activity

General Description

This activity concerns with the development of a top level ontology (called MarineTLO) that will integrate the concepts currently existing in marine-domain knowledge bases (in particular FLOD and ECOSCOPE knowledge bases). The MarineTLO-development activity is dived into six sub-activities (or Tasks) and related to each other as shown in the diagram in Fig 1.


Pic1.png

Methodology

The methodology is based on an Iterative and Incremental development approach. As such, one iteration will involve all the tasks of the Fig 1. that are described @ http://wiki.i-marine.eu/index.php/Top_Level_Ontology. All the iterations will be accurately described and evolution of the MarineTLO ontology will be released in each iteration, based on the acquirement of the specific marine domain knowledge.

Activities scheduled with deadlines

Each iteration is planned to be monitored by opening related tickets.

Related Cluster

http://wiki.i-marine.eu/index.php/Semantic_cluster_achievements

Related Wiki Pages

http://wiki.i-marine.eu/index.php/XSearch


Motivation - Goal - Requirements

At very abstract level we use the picture below as preview that focuses on viewpoints for motivations, goal and requirements of having such a ontology on top of marine-domain knowledge bases.

Motivation. Semantic technologies, applications and services for biodiversity mostly rely on the rise of an interconnected and shared tree-of-life like dataset scaling on the web. The various communities (including also marine one) are contributing to this joint effort aim to share domain data and their meaning, to provide a solid basis for biodiversity systems interoperability. One of the challenges in iMarine is how users could experice a coherent source of fact about marine resources, rather than a bag of contributed contents.

Goal. The goal in modelling and formalising MarineTLO ontology is for integrating and semantically extending the underlying models of existing marine data sources. Specifically, the MarineTLO is used on the top of a number of real and heterogeneous marine data sources, including FLOD and ECOSCOPE, as knowledge mediator to represent, manipulate and reason upon and across them.

Requirements. Focusing on Ecosystem Approach to Fisheries and Marine Resources, the MarineTLO ontology should be generic enough

  • to provide consistent abstraction or specification of concepts included in the data models or ontologies of marine data sources
  • to provide the necessary properties to make this distributed knowledge bases (FLOD, ECOSCOPE and others) a coherent source of facts, relating observation data to the respective space-temporal context and categorical domain knowledge


Slide15.jpg

Related Meetings (and their slides)

TCOM in Italy, Rome, 03.11.2012

FLOD Ontological Analysis, 7.12.2012, meeting online

TCOM in Belgium, Ostende, 29.01.2013

Semantic Cluster Meeting, online, 13.02.2013

TCOM in Italy, Pisa, 21.03.2013

TCOM in Italy, Rome, 26.03.2013

TCOM in Greece, Skiathos, 18.06.2013 (LATEST)

Analysis, Design and Implementation

FLOD Ontological Analysis

This activity has the primary goal to provide a common understanding of the FLOD ontology network. It has been considered necessary for the development of the MarineTLO. The associated ticket is https://issue.imarine.research-infrastructures.eu/ticket/888

Ecoscope Ontological Analysis

This activity has the primary goal to provide a common understanding of the ECOSCOPE ontology network. It has been considered necessary for the development of the MarineTLO. The associated ticket is https://issue.imarine.research-infrastructures.eu/ticket/889

MarineTLO Design

The activities is related to the design of MarineTLO ontology. The associated ticket is https://issue.imarine.research-infrastructures.eu/ticket/890

MarineTLO Implementation

The activities is related to the implementation of MarineTLO ontology using OWL 2 language. The associated ticket is https://issue.imarine.research-infrastructures.eu/ticket/891

MarineTLO Usage

Activities related to the usage of MarineTLO (+ references to documents/ wiki pages/ tickets). This activity is associated to the ticket https://issue.imarine.research-infrastructures.eu/ticket/900

Here, we describe possible scenarios in which MarineTLO can be evaluated. Currently, we identify the followings:

  • MarineTLO as meta-model for FLOD, ECOSCOPE and WoRMS
    • Fact Sheets and Competence Queries
  • MarineTLO as knowledge model for semantic search in X-search
    • Suppose that a user is looking for publications about tuna. Specifically he wants to find experiments that were applied to several species of tuna. So, he submits the query tuna and gets a sorted list of results and various categories of entities like Regional Fisheries Body, Species, FAO Country, etc. User realizes that the category Species may contain interesting entities. He notices that there is an entity with the label skipjack tuna which is a medium-sized fish in the tuna family found in tropical and warm-temperate waters. User wants to learn more information about that species. Specifically, he would like to see other species for which the skipjack tuna is predator or is prey. By clicking the icon next to the entity's name, user is able to instantly (at real-time) retrieve such information. In particular, in the back end, a SPARQL query is sent to the MarineTLO's endpoint asking for that information. Note that the 'Species' have been derived from FLOD, while the properties 'is predator of' and 'is prey of' have been derived from ECOSCOPE's knowledge base. That would be impossible without the exploitation of the MarineTLO.

MarineTLO Evaluation

This activity is related to the evaluation of the MarineTLO ontology. The associated ticket is https://issue.imarine.research-infrastructures.eu/ticket/892

A required activity for the MarineTLO evaluation is to populate it with concrete instances.

MarineTLO-related Products

The Notion of MarineTLO Version

Each MarineTLO version consists of

  • A release number
  • An .owl file
  • A set of competency queries
  • A short description describing the changes
  • It could also contain a set of mappings between data source and MarineTLO, each of them described as an OWL file

TODO: We also need a document that contains the scope notes of each class

Evolution Process

Since last meeting in Rome (26-03-2013), we planned to release a new version every two months (for correcting errors, based on requirements, priorities, usage needs, etc).

Version 1.0.0 released on 26-03-2013

Version 2.0.0 planned to be released by end of July 2013 (ONGOING)

  • Release Number: 2.0.0
  • Documentation of the MarineTLO version 2.0.0 https://issue.imarine.research-infrastructures.eu/ticket/1764#comment:1
  • The version 2.0.0 of the MarineTLO ontology
    • [LINK of the Version 2.0.0]
  • Competence queries
    • [LINK of the competency queries for the Version 2.0.0]
  • Mappings in OWL: FLOD-TLO, Ecoscope-TLO and WoRMS-TLO
    • [LINK of the Version 2.0.0 of the mappings in OWL ]
  • Mappings descriptions
    • [LINK of the description of the mappings in OWL ]

Previous TLO Versions

MarineTLO-based Warehouses

Warehouse 1 (June 2013)

Warehouse 2 (planned for the end of July 2013)

Ongoing

MarineTLO Related Tickets

First Iteration

  • Creation of a new TLO-based warehouse ONGOING
Retrieved from "https://wiki.d4science.org/index.php?title=Top_Level_Ontology&oldid=13634"