Difference between revisions of "Top Level Ontology"
(→FLOD Ontological Analysis) |
|||
Line 84: | Line 84: | ||
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 TLO. The associated ticket is https://issue.imarine.research-infrastructures.eu/ticket/888 | 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 TLO. The associated ticket is https://issue.imarine.research-infrastructures.eu/ticket/888 | ||
− | *'''FLOD Ontological Analysis | + | *'''FLOD Ontological Analysis''', 04-Dec-2012, |
**https://portal.i-marine.d4science.org/group/data-e-infrastructure-gateway/workspace?itemid=04d81d92-d3e3-41d9-aeaf-605bd5c4ea33 | **https://portal.i-marine.d4science.org/group/data-e-infrastructure-gateway/workspace?itemid=04d81d92-d3e3-41d9-aeaf-605bd5c4ea33 | ||
− | * '''FLOD Ontological Analysis | + | * '''FLOD Ontological Analysis''', 07-Dec-2012 |
** http://wiki.i-marine.eu/index.php/7.12.2012-TLO_FLOD_Ontological_Analysis | ** http://wiki.i-marine.eu/index.php/7.12.2012-TLO_FLOD_Ontological_Analysis | ||
− | *'''FLOD Ontological Analysis | + | *'''FLOD Ontological Analysis''', 31-Dec-2012 |
**https://portal.i-marine.d4science.org/group/data-e-infrastructure-gateway/workspace?itemid=55f18f59-d807-474b-aa5a-88b123d0dae8 | **https://portal.i-marine.d4science.org/group/data-e-infrastructure-gateway/workspace?itemid=55f18f59-d807-474b-aa5a-88b123d0dae8 | ||
Revision as of 15:26, 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 (for short TLO) that will integrate the concepts currently existing in marine-domain knowledge bases (in particular FLOD and ECOSCOPE knowledge bases). The TLO-Development activity is dived into six sub-activities (or Tasks) and related to each other as shown in the diagram in Fig 1.
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 TLO Modules/ Versions will be delivered in each iteration ready to be used.
Activities scheduled with deadlines
At least two iterations are needed to complete the TLO-Development activity with deadlines December 2012 and January 2013, respectively. Each iteration is planned to be monitored by opening related tickets. And, as in January there is going to be the next meeting, we (Claudio, Julien and Carlo) will discuss if we need a third or more iterations.
Related Cluster
http://wiki.i-marine.eu/index.php/Semantic_cluster_achievements
Related Wiki Pages
http://wiki.i-marine.eu/index.php/XSearch
Meeting In Progress
TCOM in Italy, Rome, 03.11.2012
http://wiki.i-marine.eu/index.php/03.11.2012.MeetingInRome
Meeting on "FLOD Ontological Analysis: First Iteration", 7.12.2012
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
- Agenda and Presentation, please follow the link https://portal.i-marine.d4science.org/group/data-e-infrastructure-gateway/workspace?itemid=dd36ba2b-f2fa-46ae-b5d0-1b6e2616f995
Semantic Cluster Meeting, online, 13.02.2013
- TLO activities
- Minutes from Leo: http://wiki.i-marine.eu/index.php/13.02.2013_Semantic_Cluster
TCOM in Italy, Pisa, 21.03.2013
- gCube and Production of RDF Data (FORTH side)
TCOM in Italy, Rome, 26.03.2013
- TLO-‐Acvity: Status, Open Issues and Next Steps
- Minutes of the Meeting, 27-03-2013:
TCOM in Greece, Skiathos, 18.06.2013
- We presented "TLO-related Activities
Motivation - Goal - Requirements
Describe a scenario that will justify the need for having such a TLO 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 (TLO) is for integrating and semantically extending the underlying models of existing marine data sources. Specifically, the TLO 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
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 TLO. The associated ticket is https://issue.imarine.research-infrastructures.eu/ticket/888
- FLOD Ontological Analysis, 04-Dec-2012,
- FLOD Ontological Analysis, 07-Dec-2012
- FLOD Ontological Analysis, 31-Dec-2012
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 TLO. The associated ticket is https://issue.imarine.research-infrastructures.eu/ticket/889
- ECOSCOPE Ontological Analysis, 13-Dec-2012
- ECOSCOPE Ontological Analysis, meeting, online, 11-Jan-2013
TLO Design
The activities is related to the design of TLO ontology. The associated ticket is https://issue.imarine.research-infrastructures.eu/ticket/890
- Describing the TLO design, 21-Dec-2012
- Describing the TLO design, 24-Dec-2012
TLO Implementation
The activities is related to the implementation of TLO ontology using OWL 2 language. The associated ticket is https://issue.imarine.research-infrastructures.eu/ticket/891
- Please loot at http://wiki.i-marine.eu/index.php/Top_Level_Ontology#TLO_Products for the versions of the TLO
- SPARQL endpoints (Virtuoso and OWLIM-Lite)
- Competency queries
TLO Results
TLO Usage
Activities related to the usage of TLO (+ 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 TLO can be evaluated. Currently, we identify the followings:
- TLO as meta-model for FLOD, ECOSCOPE and WoRMS
- Fact Sheets and Competence Queries
- TLO 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 TLO'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 TLO.
TLO Evaluation
This activity is related to the evaluation of the TLO 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.
- To populate just the class Species, please follow the link
- To populate the class Species with predator and prey relationships, please follow the link
- Competence Queries, 22-03-2013
- TLO Populating, 22-03-2013
- TLO Evaluation Report, 22-04-2013
TLO Products
Each TLO 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 TLO, 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
- Release Number: 1.0.0
- Documentation of the TLO version 1.0.0 https://issue.imarine.research-infrastructures.eu/ticket/1764#comment:1
- This version of the TLO containing classes, properties and instances to test the TLO over the fact sheet
- Competence queries covering the fact sheets
- OWL Mappings: FLOD-TLO, Ecoscope-TLO and WoRMS-TLO
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
Current TLO-based repository
- Virtuoso
TLO Related Tickets
First Iteration
- FLOD Ontological Analysis: https://issue.imarine.research-infrastructures.eu/ticket/888 CLOSED
- Ecoscope Ontological Analysis: https://issue.imarine.research-infrastructures.eu/ticket/889 CLOSED
- TLO Design: https://issue.imarine.research-infrastructures.eu/ticket/890 CLOSED
- TLO Implementation: https://issue.imarine.research-infrastructures.eu/ticket/891 CLOSED
- TLO Results: TLO Usage https://issue.imarine.research-infrastructures.eu/ticket/900 CLOSED
- TLO Evaluation, https://issue.imarine.research-infrastructures.eu/ticket/892 CLOSED
- TLO Instatiation, https://issue.imarine.research-infrastructures.eu/ticket/1220 OPEN