Buffalo Ontology Site. Institute for Formal Ontology and Medical Information Science (IFOMIS) Bio Ontology Research Group Leipzig - Main - GFO-Bio. We create a biomedical core ontology based on the top-level ontology GFO (General Formal Ontology?). There are versions in OWL which can be tried, and any input is very much appreciated. You will need a DL reasoner to classify the ontology. We recommend the use of SWOOP, which comes with the Pellet reasoner. 1. The CVS repository for GFO-Bio can be found on Savannah. 2. The URI of the ontology is and If you use an ontology editor such as SWOOP, just enter the URI in the appropriate field. gfo-bio.owl is an ontology of individuals, and it is similar in this sense to the Simple Bio Upper Ontology or the BioTop ontology. gfo-bio-meta.owl is an ontology of categories.
Using and together will yield OWL-Full, for which a reasoner such as Euler could be used. 3. 4. Simple Bio Upper Ontology. We recommend implementing domain ontologies around a skeleton of disjoint trees of primitives using the methods for normalisation described in Modularisation of domain ontologies implemented in description logicsand related formalisms including OWL. We recommend implementing upper ontologies as a series of dichotomies following a twenty questions model as shown below. The purpose of these demonstrations is to provide a simple upper ontology suitable for biomedicine and show how the Top domain ontology for biomedicine links to it. III Background - an engineering approach to upper ontologies The simple-bio-upper-ontology is described below. This section gives a bit of motivation.
If you just want to download the ontology, you may skip this part and go straight to the implementation and download. Upper ontologies are different from domain ontologies. This upper ontology is intended to serve three purposes: Comments and suggestions are welcome to rector@cs.man.ac.uk. BEWARE. This file. ID policy. Note: This section references OBO specification version 1.3, which is deprecated. Readers should consider this section as background material. OBO 1.3 [7,8] introduces identifier expressions that can be taken as a kind of macro that expands into a logical definition. Although the surface syntax of id expressions conforms to the OBO format for identifiers they are not considered identifiers but rather shorthand for un-named class expressions which should be expanded (see [8] sec 4.1) MC: [8] 4.1 is "4.1 Relation to OBO-Format 1.2 " Should it be 4.11? AR: TOC of sync: Chris FIXMEbefore applying the id mapping policy.
Example of ID Definitional Expressions: GO:0005737^part_of(CL:0000023) can be used wherever one wants to say "cytoplasm of oocyte". [Term] id: GO:0005737^part_of(CL:0000023) intersection_of: GO:0005737 ! Policy for OBO Foundry ontologies Response to Web requests for OBO URIs It is expected that the Foundry-compliant URIs behave, on the web, usefully. Allocating IDSPACEs Tracker: