Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

This repository is for OntoDBSchema 2

You are looking at the repository of OntoDBSchema for OntoDB version 2. The repository of OntoDBSchema for OntoDB version 1 is OntoDBSchema_v2.

Please refer to OntoDB repository to have a big picture of OntoDB ontology based database tool.


The OntoDB architecture has been initially designed for storing PLIB ontologies and their instances. As the PLIB ontology language regularly evolves and because several other ontology languages exist, the first objective of this architecture was to support evolutions of the used ontology language. This architecture was to design an OntoDB is implemented on top of the PostgreSQL DB-MS. It has a four-parts architecture depicted in the next figure.

OntoDB Schema

The data part (2)

The data part uses the horizontal storage layout. In this storage layout, a table is associated to each concrete class. Each one of these tables has a column named rid to identify class instances. In addition, this table has one column for each property used by at least one instance of this class. To defi ne the link between an instance and its belonging class, the name of a table (resp. of a column) is the concatenation of "E" (resp. "P") with the identi fier of the corresponding class (resp. property).

The ontology part (3)

It contains all the ontologies that de ne the semantics of the various domains covered by the database. OntoDB supports the PLIB ontology model which includes the core ontology model of OntoQL. Thus, this part contains a set of table to store PLIB ontologies.

The metaschema part (4)

The meta-schema part records the ontology model used. For the ontology part, the meta schema part plays the same role as the one played by the metabase in traditional databases systems. In previous figure (2), two tables based on a UML meta-model are used to store the entity class and its attribute name. OntoQL statements have been implemented according to this architecture.

The system catalog part (1)

The system catalog is a traditional part of any DBMS. It contains system tables used to manage all the data contained in the database. In OntoDB, it contains speci cally the description of all the tables and columns de ned in the three other parts of this architecture.


The OntoDB schema can be downloaded into the sql directory.

Software requirements

OntoDBSchema can be deployed to:

  • Postgresql
  • Oracle

Installation with Postgresql

  • Import the ontology based data base template_ontodb
$ createdb -U postgres template_ontodb
$ psql -U postgres template_ontodb < template_ontodb_postgresql.sql

Software licence agreement

Details the license agreement of OntoDBSchema V2: LICENCE

Historic Contributors (core developers first followed by alphabetical order)


An ontology based database tool, support of multiple ontology models within ontology based database. This repository is related to the second version of OntoDB.