Difference between revisions of "Top Level Ontology"
| Line 1: | Line 1: | ||
| − | + | == TLO-Development activity == | |
| − | + | ||
| − | + | === 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. | 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. | ||
| Line 10: | Line 7: | ||
[[File:Slide37.jpg]] | [[File:Slide37.jpg]] | ||
| − | + | === Methodology === | |
| − | + | ||
| − | + | ||
It is based 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. | It is based 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. | 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. | ||
Revision as of 17:27, 29 November 2012
TLO-Development activity
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 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.
Motivation / Scenario
Describe a scenario that will justify the need for having such a TLO on top of marine-domain knowledge bases.
FLOD Ontological Analysis
The ontological analysis of FLOD (+ references to documents/ wiki pages/ tickets). This activity is associated to the ticket https://issue.imarine.research-infrastructures.eu/ticket/888
Ecoscope Ontological Analysis
The ontological analysis of Ecoscope (+ references to documents/ wiki pages/ tickets). This activity is associated to the ticket https://issue.imarine.research-infrastructures.eu/ticket/889
TLO Design
The activities carried out towards the design of TLO (+ references to documents / wiki pages/ tickets). This activity is associated to the ticket https://issue.imarine.research-infrastructures.eu/ticket/890
TLO Implementation
The activities carried out for the implementation of TLO (+ references to documents/ wiki pages/ tickets). This activity is associated to the ticket https://issue.imarine.research-infrastructures.eu/ticket/891
TLO Evaluation
Activities related to the evaluation of TLO (+ references to documents/ wiki pages/ tickets). This activity is associated to the ticket https://issue.imarine.research-infrastructures.eu/ticket/892
