Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
ontodm-core [2014/09/15 14:47]
admin
ontodm-core [2016/04/12 10:56] (current)
admin [Release version 1]
Line 22: Line 22:
 For representing the mining of structured data, we import the [[ontodt|OntoDT ontology of datatypes]]. Classes that are referenced and reused in OntoDM-core are imported into the ontology by using the [[http://​obi-ontology.org/​page/​MIREOT|Minimum Information to Reference an External Ontology Term (MIREOT) principle]] ​ and extracted using the [[http://​ontofox.hegroup.org|OntoFox]] web service. For representing the mining of structured data, we import the [[ontodt|OntoDT ontology of datatypes]]. Classes that are referenced and reused in OntoDM-core are imported into the ontology by using the [[http://​obi-ontology.org/​page/​MIREOT|Minimum Information to Reference an External Ontology Term (MIREOT) principle]] ​ and extracted using the [[http://​ontofox.hegroup.org|OntoFox]] web service.
 =====Ontology Structure===== =====Ontology Structure=====
-For the domain of DM, we propose a horizontal description structure that includes three layers: ​+For the domain of DM, we propose a [[layers|horizontal description structure that includes three layers]]
   * a specification layer, ​   * a specification layer, ​
   * an implementation layer, and    * an implementation layer, and 
Line 28: Line 28:
 Having all three layers represented separately in the ontology will facilitate different uses of the ontology. For example, the specification layer can be used to reason about data mining algorithms; the implementation layer can be used for search over implementations of data mining algorithms and to compare various implementations;​ and the application layer can be used for searching through executions of data mining algorithms. ​ Having all three layers represented separately in the ontology will facilitate different uses of the ontology. For example, the specification layer can be used to reason about data mining algorithms; the implementation layer can be used for search over implementations of data mining algorithms and to compare various implementations;​ and the application layer can be used for searching through executions of data mining algorithms. ​
  
-This description structure is based on the use of the upper-level ontology [[http://​www.ifomis.org/​bfo/​|BFO]] and the extensive reuse of classes from the mid-level ontologies [[http://​obi-ontology.org/​page/​Main_Page|OBI]] and [[https://​code.google.com/​p/​information-artifact-ontology/​|IAO]]. The proposed three layer description structure is orthogonal to the vertical ontology architecture which comprises ​ an:  
-  * upper-level, ​ 
-  * a mid-level, and  
-  * a domain level. ​ 
-This means that each vertical level contains all three description layers. ​ 
-==== Layers ==== 
-{{ ::​fig1-page1.png?​400|}} 
-The specification layer contains //BFO: generically dependent continuants//​ at the upper-level,​ and //IAO: information content entities// at the mid-level. In the domain of data mining, example classes are //data mining task// and //data mining algorithm//​. ​ 
  
-The implementation layer describes //BFO: specifically dependent continuants//,​ such as //BFO: realizable entities// (entities that are executable in a process). At the domain level, this layer contains classes that describe the implementations of algorithms. ​ 
- 
-The application layer contains classes that aim at representing processes, e.g., extensions of //BFO: processual entity//. Examples of (planned) process entities in the domain of data mining are the execution of a data mining algorithm and the application of a generalization on new data, among others. 
-==== Relations between layers ==== 
- 
-The entities in each layer are connected using general relations, that are layer independent,​ and layer specific relations. Examples of general relations are //is-a// and //​part-of//:​ they can only be used to relate entities from the same description layer. For example, an information entity (member of the specification layer) can not have as parts processual entities (members of the application layer). Layer specific relations can be used only with entities from a specific layer. For example, the relation //​precedes//​ is only used to relate two processual entities. The description layers are connected using cross-layer relations. An entity from the specification layer //​is-concretized-as//​ an entity from the implementation layer. Next, an implementation entity //​is-realized-by//​ an application entity. Finally, an application entity, e.g., a planned process //​achieves-planned-objective//,​ which is a specification entity. 
 =====Key OntoDM-core classes===== =====Key OntoDM-core classes=====
-The ontology includes the representation of the following entities: [[data|data]],​ [[data mining task|data mining task]], [[generalization|generalization]],​ [[data mining algorithm|data mining algorithm]],​ [[constraints|constraints and constraint based data mining tasks and algorithms]],​ and [[data mining scenario|data mining scenario]]. +The ontology includes the representation of the following entities: ​ 
-{{ :​ontodm-coreentities.png?​direct&​600 |}}+{{ :​ontodm-coreentities.png?​600|}} 
 +  * [[data|data]], ​ 
 +  * [[data mining task|data mining task]], ​ 
 +  * [[generalization|generalization]], ​ 
 +  * [[data mining algorithm|data mining algorithm]], ​ 
 +  * [[constraints|constraints and constraint based data mining tasks and algorithms]],​ and  
 +  * [[data mining scenario|data mining scenario]].
  
 +===== Ontology evaluation =====
 +We assess the quality of OntoDM-core from three different evaluation aspects:
 +  * [[ontology metrics|we analyze a set of ontology metrics]]; ​
 +  * [[design criteria assessment|assess how well the ontology meets a set of predefined design criteria and ontology best practices]];​ and 
 +  * [[competency questions assessment|assess the ontology toward a set of competency questions]].
  
  
Line 64: Line 61:
 {{ :​file_structure.jpg?​direct&​300|}} {{ :​file_structure.jpg?​direct&​300|}}
   * All files in one zip archive{{:​ontodm_v_1_r.zip|OntoDM-coreV1.zip}}   * All files in one zip archive{{:​ontodm_v_1_r.zip|OntoDM-coreV1.zip}}
-  * OntoDM-core main file [[http://kt.ijs.si/panovp/​OntoDM/​OntoDM.owl|OntoDM-core.owl]] +  * OntoDM-core main file [[http://ontodm.com/ontodm-core/​OntoDM.owl|OntoDM-core.owl]] 
-  * File that OntoDM-core imports directly and contains external classes [[http://kt.ijs.si/panovp/​OntoDM/​external.owl|external.owl]] +  * File that OntoDM-core imports directly and contains external classes [[http://ontodm.com/ontodm-core/​external.owl|external.owl]] 
-  * File that external file imports and contains OBI classes[[http://​kt.ijs.si/panovp/​OntoDM/​external-OBI.owl|external-OBI.owl]] +  * File that external file imports and contains OBI classes [[http://ontodm.com/ontodm-core/​external-OBI.owl|external-OBI.owl]] 
-  * OntoDT ontology of datatypes [[http://kt.ijs.si/panovp/​OntoDM/​OntoDT.owl|OntoDT.owl]]+  * OntoDT ontology of datatypes [[http://ontodm.com/ontodm-core/​OntoDT.owl|OntoDT.owl]]
   * {{:​clus_instances.owl}}   * {{:​clus_instances.owl}}
   * {{:​clus_inferred.owl}}   * {{:​clus_inferred.owl}}

QR Code
QR Code OntoDM-core - Ontology of Core Data Mining Entities (generated for current page)