wiki:DesignRationale/OntologiesVsTaxonomies

Ontologies or Taxonomies in OrganiK?

The question of classification of documents did come up. Our agreement on this topic was reached in ticket:16. Further discussion should be done in ticket:16, and this page updated.

We agreed to classify documents to terms in a taxonomy which can be managed in the SemanticApi. A taxonomy can be detailled or not, and can be as complex as an ontology with classes, properties, rules, inference and more. What did we pick for OrganiK and why?

We agreed in the telcos and in D2.1 to use taxonomies without properties and rules.

Will OrganiK be integrated with public ontologies, will it be prepopulated with classes from a public ontology? Will it contain "Person, Organisation, Place, Bug, Project, Relase" as terms?

  1. no, each taxonomy for each company starts empty
  2. yes, core classes predefined by the software are contained (i.e. opencalais can detect Person and represents it as Person in an ontology which we could map to our own class). That means we should map the taxonomy terms to external ontology terms via some database extension to the drupal taxonomy module (currently, a drupal taxonomy term cannot link to outside ontologies, afaik)
  3. yes, core classes (A2) and another taxonomy with more classes

We agreed to start with an empty system (a) with the option to predefine core classes when needed (b). If OrganiK needs a predefined taxonomy, we should keep it in a core level and - if possible - common for all SMEs (=installations). The PIMO ontology may be a starting point, or Dolce/Sumo/Opencyc?.

Last modified 8 years ago Last modified on 06/22/09 16:51:18