Ontology Alignment Evaluation Initiative - OAEI-2008 CampaignOAEI
The OAEI-2008 results are available here

Ontology Alignment Evaluation Initiative

2008 Campaign

The increasing number of methods available for schema matching/ontology integration suggests the need to establish a consensus for evaluation of these methods. Since 2004, OAEI organizes evaluation campaigns aiming at evaluating ontology matching technologies (see http://oaei.ontologymatching.org/2004/Contest/, http://oaei.ontologymatching.org/2005, http://oaei.ontologymatching.org/2006, and http://oaei.ontologymatching.org/2007).

The OAEI 2008 campaign is associated to the ISWC Ontology matching workshop to be held at Karlsruhe, Germany on Sunday October 26, 2008.


This year's campaign consists of four tracks gathering eight data sets and different evaluation modalities.

Comparison track: benchmark2008
Like in previous campaigns, a systematic benchmark series has been produced. The goal of this benchmark series is to identify the areas in which each alignment algorithm is strong and weak. The test is based on one particular ontology dedicated to the very narrow domain of bibliography and a number of alternative ontologies of the same domain for which alignments are provided.
Expressive ontologies
The anatomy real world case is about matching the Adult Mouse Anatomy (2744 classes) and the NCI Thesaurus (3304 classes) describing the human anatomy.
features networked ontologies from domains related to fisheries manipulated by the Food and Agricultural Organization of the United Nations (FAO).
Directories and thesauri
The directory real world case consists of matching web sites directories (like open directory or Yahoo's). It is more than 4 thousand elementary tests.
The mldirectory real world case consists of matching web sites directories (like Dmoz, Licos and Yahoo's) in different languages (English and Japanese). These are exerpts of the directories which contain around one thousand categories.
Two SKOS thesauri about books have to be aligned using relations from the SKOS Mapping vocabulary. Samples of the results are evaluated by domain experts.
very large crosslingual resources
This real world test case requires matching of very large resources (vlcr) available on the web, viz. DBPedia, WordNet and the Dutch audiovisual archive (GTAA), DBPedia is multilingual and GTAA is in Dutch.
Consensus workshop: conference
Participants will be asked to freely explore a collection of ontologies used for organising conferences (the domain being well understandable for every researcher) with regard to two possible tasks (generic correspondences or application-specific correspondences). Results will be evaluated a posteriori in part manually and in part by data-mining techniques and logical reasoning techniques. There will also be evaluation against reference mapping based on small subset of the whole collection.

We summarize below the variation between the results expected by these tests (all results are given in the Alignment format):

benchmarksOWL=[0 1]openEN(36+61)*2*49
anatomyOWL=[0 1]blindEN3k*3k
conferenceOWL-DL=, <=[0 1]blind+consensualEN
[0 1] in the 'confidence-column' means that submission with confidence values in the range [0 1] are preferred, but does not exclude systems which do not distinguish between different confidence values.

Evaluation process

Each data set has a different evaluation process. They can be roughly divided into four groups:

benchmark: open
benchmark tests are provided with the expected results. Participants must return their obtained results to organisers;
anatomy, directory, mldirectory, library, vlcr: blind
these are blind tests, i.e., participants do not know the results and must return their results to organisers;
fao: expert
the results themselves are evaluated by experts a posteriori on a sample of the results;
conference: consensus
requires that participants send their results to organisers, the results are not pre-determined through reference alignments but computed and/or discussed as a consensus among given results.

However, the evaluation will be processed in the same three successive steps as before.

Preparatory Phase

Ontologies are described in OWL-DL and serialized in the RDF/XML format. The expected alignments are provided in the Alignment format expressed in RDF/XML.

The ontologies and alignments of the evaluation are provided in advance during the period between May 19th and June 15th. This gives potential participants the occasion to send observations, bug corrections, remarks and other test cases to the organizers. The goal of this primary period is to be sure that the delivered tests make sense to the participants. The feedback is important, so all participants should not hesitate to provide it. The tests will certainly change after this period, but only for ensuring a better participation to the tests. The final test base has been released on July 1st.

Execution Phase

During the execution phase the participants will use their algorithms to automatically match the ontologies. Participants should only use one algorithm and the same set of parameters for all tests in all tracks. Of course, it is fair to select the set of parameters that provide the best results (for the tests where results are known). Beside the parameters the input of the algorithms must be the two provided ontology to match and any general purpose resource available to everyone (that is no resourse especially designed for the test). In particular, participants should not use the data (ontologies and results) from other test sets to help their algorithm. And cheating is not fair...

The deadline for delivering final results is September 26th, sharp. However, it is highly advised that participants send results before (preferably by September 1st) to the organisers so that they can check that they will be able to evaluate the results smoothly and can provide some feedback to participants.

Participants will provide their alignment for each test in the Alignment format. The results will be provided in a zip file containing one directory per test (named after its number) and each directory containing one result file in the RDF/XML Alignment format with always the same name (e.g., participant.rdf replacing "participant" by the name you want your system to appear in the results, limited to 6 alphanumeric characters). This should yield the following structure:

+- benchmarks
|  +- 101
|  |  +- participant.rdf
|  +- 103
|  |  +- participant.rdf
|  + ...
+- anatomy
|  +- 1
|  |  +- participant.rdf
|  +- 2
|  |  +- participant.rdf
|  +- ...
+- directory
|  +- 1
|  |  +- participant.rdf
|  + ...
+ ...

Participants will also provide, for September 26th, a paper to be published in the proceedings and a link to their program and parameter set.

The only interesting alignments are those involving classes and properties of the given ontologies. So the alignments should not align individuals, nor entities from the external ontologies.

Evaluation Phase

The organizers will evaluate the results of the algorithms used by the participants and provide comparisons on the basis of the provided alignments.

In order to ensure that it will be possible to process automatically the provided results, participants are requested to provide (preliminary) results by September 1st. In the case of blind tests only the organizers will do the evaluation with regard to the withheld alignments. In the case of double blind tests, the participants will provide a version of their system and the values of the parameters if any.

An email with the location of the required zip files must be sent to the contact addresses below.

The standard evaluation measures will be precision and recall computed against the reference alignments. For the matter of aggregation of the measures we will use weighted harmonic means (weight being the size of reference alignment). Precision/recall graphs will also be computed, so it is advised that participants provide their results with a weight to each correspondence they found (participants can provide two alignment results: <name>.rdf for the selected alignment and <name>-full.rdf for the alignment with weights.

Furthermore, it is planned to introduce new measures addressing some limitations of precision and recall. These will be presented at the workshop discussion in order for the participants to provide feedback on the opportunity to use them in a further evaluation.


May 19th
datasets are out
June 15th
end of commenting period
July 1st
tests are frozen
September 1st
participants send preliminary results (for interoperability-checking)
September 26th
participants send final results and papers
October 10th
organisers publish results for comments
October 26th-27th
final results ready and OM-2008 workshop.


From the results of the experiments the participants are expected to provide the organisers with a paper to be published in the proceedings of the workshop. The paper must be no more than 8 pages long and formatted using the LNCS Style. To ensure easy comparability among the participants it has to follow the given outline. A package with LaTeX and Word templates is made available here. The above mentionned paper must be sent in PDF format by September 26th to Pavel Shvaiko (pavel () dit dot unitn dot it) with copy to Jerome . Euzenat () inrialpes . fr.

Participants may also submit a longer version of their paper, with a length justified by its technical content, to be published online in the CEUR-WS collection and on the OAEI web site (this last paper will be due just before the workshop).

The outline of the paper is as below (see templates for more details):

These papers are not peer-reviewed and are here to keep track of the participations and the description of matchers which took part in the campaign.

The results from both selected participants and organizers will be presented at the Workshop on Ontology matching at ISWC 2008 taking place at Karlsruhe (Germany) on October, 26th, 2008. We hope to see you there.

Tools and material

Here are some tools that may help participants.

Processing tools

Participants may use the Alignment API for generating and manipulating their alignments (in particular for computing evaluation of results).

SKOS conversion tools

The participants may use various options if they need to convert SKOS vocabularies into OWL.

OWL-N3 conversion tools

Vassilis Spiliopoulos pointed out to Altova transformer from OWL to N3 notation. This can be useful for some. This is a commercial tool with a 30 days free trial.


$Id: index.html,v 1.15 2009/04/19 11:50:12 euzenat Exp $