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

Ontology Alignment Evaluation Initiative

2010 Campaign

The increasing number of methods available for schema matching/ontology integration necessitate to establish a consensus for evaluation of these methods. Since 2004, OAEI organizes evaluation campaigns aiming at evaluating ontology matching technologies.

The OAEI 2010 campaign is associated to the ISWC Ontology matching and the Evaluation of semantic technologies workshops held in Shanghai, China in November, 2010.


The 2010 campaign introduces a new evaluation modality in association with the SEALS project. Its goal is to provide more automation to the evaluation and more direct feedback to the participants. The concerned datasets are benchmark, conference and anatomy. Participants in this modality must follow the specific instructions for participation.

Comparison track: benchmark
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.
The goal of this track is to find all correct correspondences within a collection of ontologies describing the domain of organising conferences (the domain being well understandable for every researcher). Additionally, 'interesting correspondences' are also welcome. Results will be evaluated automatically against reference alignment and by data-mining and logical reasoning techniques. Sample of correspondences and 'interesting correspondences' will be evaluated manually.
Directories and thesauri
The directory real world case consists of matching web site directories (like open directory or Yahoo's). This year the track consists of two modalities, the first is composed by more than 4 thousand elementary tests, and the second is composed by a single test which matches two big directories (2854 and 6555 nodes each).
Instance matching
The instance data matching track aims at evaluating tools able to identify similar instances among different RDF and OWL datasets. It features Web datasets, as well as a generated benchmark.
This task (imei) is focused on RDF and OWL data in the context of the Semantic Web. Participants will be asked to execute their algorithms against various datasets and their results will be evaluated by comparing them with a pre-defined reference alignment. Participating systems are free to use any combination of matching techniques and background knowledge. Results, in the alignment format, will be evaluated according to standard precision and recall metrics.
very large crosslingual resources
The purpose of this task (vlcr) is (1) to create alignments between large thesauri in different languages and (2) to align these thesauri to other sources on the Linked Data Web. This is seen as a step towards opening up and connecting large collections of data all around the world. In the vlcr task we align three resources to each other: the Thesaurus of the Netherlands Institute for Sound and Vision (called GTAA), the New York Times subject headings and DBpedia.

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

testsealslanguagerelationsconfidenceModalitiesLanguageSize (≈)
benchmarksOWL=[0 1]openEN(36+61)^2*49
anatomyOWL=[0 1]blindEN3k*3k
conferenceOWL-DL=, <=[0 1]blind+openEN(20^2)*21
imeiRDF=[0 1]blindEN
exactMatch[0 1]blind
[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;
anatomy, conference, imei: blind
these are blind tests, i.e., participants do not know the results;

For the tracks included in the new modality, namely benchmark, conference and anatomy, the participants must run their tools in the SEALS platform, following the instructions. For the other tracks, the participants must return their results to organisers.

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 June 1st and June 21st. 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 bases will be released on July 5th.

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 resource 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 October 4th, sharp.

For old-style tracks, it is highly advised that participants send results before (preferably by August 30th) 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
|  + ...
+ ...

For the SEALS modality, participants must register their tools by that time in the SEALS portal (see instructions) and must test their web service implementation in the SEALS platform (see instructions). Participants must guarantee that their tools generate alignments in the correct format (Alignment API).

All participants will also provide, for October 4th, a paper to be published in the proceedings

All participants are required to provide a link to their program and parameter set.

Apart from the instance matching track, the only interesting alignments are those involving classes and properties of the given ontologies. So these 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 August 30th (old-style tracks). 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. Additionally, with the help of the SEALS platform, we will be able to measure runtime and alignment coherence for the anatomy and conference tracks.


June 1st
datasets are out
June 21st
end of commenting period
July 8th
tests are frozen
August 30th
participants send preliminary results for interoperability-checking (old-style tracks), or ensure that their tools work under the SEALS platform (SEALS tracks, see further instructions for at the Execution phase)
October 4th
participants send final results (old-style tracks) or register their final results in the SEALS platform (SEALS tracks). All participants must send their papers.
November 7th
final results ready and OM-2010 workshop and evaluation of semantic technologies workshop.
November 30th
participants send final versions of papers to Cassia Trojahn and Pavel Shvaiko.


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 Ontology matching 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 before October 4th to Cassia . Trojahn (a) inrialpes . fr with copy to pavel (a) dit . unitn . it.

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 workshops).

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

  1. Presentation of the system
    1. State, purpose, general statement
    2. Specific techniques used
    3. Adaptations made for the evaluation
    4. Link to the system and parameters file
    5. Link to the set of provided alignments (in align format)
  2. Results
  3. General comments
    (not necessaryly by putting the section below but preferably in this order).
    1. Comments on the results (strength and weaknesses)
    2. Discussions on the way to improve the proposed system
    3. Comments on the OAEI procedure (including comments on the SEALS evaluation, if relevant)
    4. Comments on the OAEI test cases
    5. Comments on the OAEI measures
    6. Proposed new measures
  4. Conclusions
  5. References

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 Ontology matching workshop and at the Evaluation of semantic technologies workshop (for the tracks using the SEALS platform) at ISWC 2010 taking place at Shanghai (CN) in November, 2010. We hope to see you there.

Tools and material

Here are some tools that may help participants.

SEALS platform

The instruction for using the SEALS platform are available here.

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.9 2010/07/08 10:06:45 euzenat Exp $