Difference between revisions of "Top Level Ontology"

From D4Science Wiki
Jump to: navigation, search
Line 159: Line 159:
 
== MarineTLO-related Products ==
 
== MarineTLO-related Products ==
  
−
=== The Notion of Version  ===
+
=== The Notion of MarineTLO Version  ===
  
 
Each MarineTLO version consists of
 
Each MarineTLO version consists of
Line 185: Line 185:
 
** https://portal.i-marine.d4science.org/group/data-e-infrastructure-gateway/workspace?itemid=0745f853-f81c-4317-ac72-b0e78c4fdaeb
 
** https://portal.i-marine.d4science.org/group/data-e-infrastructure-gateway/workspace?itemid=0745f853-f81c-4317-ac72-b0e78c4fdaeb
  
−
=== Previous TLO Versions ===
+
==== Previous TLO Versions ====
 
* TLO Version 13/11/2012, https://portal.i-marine.d4science.org/group/data-e-infrastructure-gateway/workspace?itemid=832af2c7-70d2-4ac3-8985-ed1efcaa0a40
 
* TLO Version 13/11/2012, https://portal.i-marine.d4science.org/group/data-e-infrastructure-gateway/workspace?itemid=832af2c7-70d2-4ac3-8985-ed1efcaa0a40
  
−
== Current MarineTLO-based repository ==
+
=== The Notion of MarineTLO-based Warehouses ===
 +
 
 +
==== Warehouse 1 (June 2013) ====
 
* Virtuoso  
 
* Virtuoso  
 
**http://62.217.127.213:8890/sparql with graph name http://www.ics.forth.gr/isl/TLObasedDataWarehouse
 
**http://62.217.127.213:8890/sparql with graph name http://www.ics.forth.gr/isl/TLObasedDataWarehouse
Line 194: Line 196:
 
* OWLIM Lite
 
* OWLIM Lite
 
**http://62.217.127.213:8080/openrdf-workbench/repositories/TLODataWarehouse/
 
**http://62.217.127.213:8080/openrdf-workbench/repositories/TLODataWarehouse/
 +
 +
==== Warehouse 2 (July 2013) ====
 +
 +
Ongoing
  
 
* Browse Virtuoso MarineTLO-based repository @ http://62.217.127.128:8890/fct/
 
* Browse Virtuoso MarineTLO-based repository @ http://62.217.127.128:8890/fct/

Revision as of 22:24, 2 July 2013

Person responsible for editing/maintaining this page

  • Carlo Allocca (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

It is based on an Iterative and Incremental development approach. As such, one iteration will involve all the above tasks that are described here http://wiki.i-marine.eu/index.php/Top_Level_Ontology. All the iterations will be accurately described and new MarineTLO version will be delivered in each iteration.

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

Describe a scenario that will justify the need for having such a MarineTLO on top of marine-domain knowledge bases.

THE MOTIVATIONS ARE BASED ON THE FACT THAT: 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.

THE GOAL IS: Our goal in modelling and formalising a Top Level Ontology (MarineTLO) 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.

THE REQUIREMENTS ARE: This Top Level Ontology has to focus on EAF ( Ecosystem Approach to Fisheries / Marine Resources) and should be generic enough to provide consistent abstractions or specifications of concepts included in all data models or ontologies of iMarine data sources such as ECOSCOPE, TDWG-WORMS, FLOD, AGROVOC, DwC, IBIS [Gangemi 2002], [Doerr 2003], and provide the necessary properties to make this distributed knowledge base a coherent source of facts relating observational data with the respective spatiotemporal context and categorical (systematic) domain knowledge

Related Meetings (and their slides)

TCOM in Italy, Rome, 03.11.2012

http://wiki.i-marine.eu/index.php/03.11.2012.MeetingInRome

FLOD Ontological Analysis, 7.12.2012, meeting online

For the details of the first meeting, please follow the link http://wiki.i-marine.eu/index.php/7.12.2012-TLO_FLOD_Ontological_Analysis. This meeting is related to the ticket https://issue.imarine.research-infrastructures.eu/ticket/224#comment:15

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

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

Previous TLO Versions

The Notion of MarineTLO-based Warehouses

Warehouse 1 (June 2013)

Warehouse 2 (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=13570"