You are here: indexactivitiestheme1projectsontocondor

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
activities:theme1:projects:ontocondor [2021/01/28 11:38]
gibaud
activities:theme1:projects:ontocondor [2021/01/28 11:48] (current)
gibaud
Line 2: Line 2:
  
 This ontology was developed to address the needs expressed by the CONDOR project. This ontology was developed to address the needs expressed by the CONDOR project.
- 
- 
  
 The ontology was designed as an application ontology gathering all entities and relationships involved. ​ The ontology was designed as an application ontology gathering all entities and relationships involved. ​
-It extends the OntoSPM ontology, a general-purpose ontology for Surgical Process Models.+It extends the OntoSPM ontology, a general-purpose ontology for Surgical Process Models ​designed in the context of the [[https://​ontospm.univ-rennes1.fr/​doku.php?​id=start| OntoSPM collaborative Action]].
  
 The choice of classes and the relationships that bind them derive from the functional needs expressed in CONDOR, namely mainly, the annotation of surgical videos: The choice of classes and the relationships that bind them derive from the functional needs expressed in CONDOR, namely mainly, the annotation of surgical videos:
Line 16: Line 14:
   * visibility of objects in images of the videos.   * visibility of objects in images of the videos.
  
-The ontology is organized as a set of files represented in OWL, the Web Ontology Language +The ontology is organized as a set of files represented in OWL, the Web Ontology Language
-{{:​activities:​theme1:​projects:​ontocondorontology-imports.png?​500| Figure 1}}.+OntoSPM and OntoCONDOR reused as much as possible existing ontological resources. Therefore, we adopted an organization in modules, in which the root application ontology (called OntoCONDOR) imports OntoSPM, which imports several extracts of existing ontologies.  
 + 
 +{{:​activities:​theme1:​projects:​ontocondorontology-imports.png?​500| Figure 1}}
  
-OntoSPM and OntoCONDOR reused as much as possible existing ontological resources. Therefore, we adopted an organization in modules, in which the root application ontology (called OntoCONDOR) imports OntoSPM, which imports several extracts of existing ontologies. ​These extracts, e.g. from the Foundational Model of Anatomy, the Units Ontology (UO), the Phenotype and Trait Ontology (PATO) were generated using the OntoFox tool, based on the MIREOT model. The overall integration of these disparate ingredients relied on the common philosophical ground provided by the Basic Formal Ontology (BFO version 23).+These extracts, e.g. from the Foundational Model of Anatomy, the Units Ontology (UO), the Phenotype and Trait Ontology (PATO) were generated using the OntoFox tool, based on the MIREOT model. The overall integration of these disparate ingredients relied on the common philosophical ground provided by the Basic Formal Ontology (BFO version 23).
  
 In terms of application,​ OntoCONDOR focuses on the two procedures considered in CONDOR, namely: In terms of application,​ OntoCONDOR focuses on the two procedures considered in CONDOR, namely:
Line 34: Line 34:
 Two zip files are provided. Two zip files are provided.
  
-  ​a zip containing only the extension (i.e. OntoSPM files are not included, but can be retrieved automatically from the web) (i.e. OntoSPM files are not included)[[:​activities:​theme1:​projects:​ontocondorfinalwithoutontospm.zip|OntoCONDOR without OntoSPM]]+  ​a zip containing only the extension (i.e. OntoSPM files are not included, but can be retrieved automatically from the web) {{:​activities:​theme1:​projects:​ontocondorfinalwithoutontospm.zip|OntoCONDOR without OntoSPM}}
-  ​a zip containing all files (i.e. OntoSPM files are included) +  ​a zip containing all files {{:​activities:​theme1:​projects:​ontocondorfinalwithontospm.zip|OntoCONDOR with OntoSPM}}.
-[[:​activities:​theme1:​projects:​ontocondorfinalwithontospm.zip|OntoCONDOR with OntoSPM]].+
    
  
  
  
inserm rennes1 ltsi