Process Model Matching @ OAEI 2016

This page informs about the Process Model Matching track, which is a new OAEI track in 2016. We provide a short description and link to the relevant resources.


In 2013 and again in 2015 the community interested in process modeling conducted an evaluation campaign similar to the OAEI. Instead of matching ontologies, the task was to match process models described in different formalisms like BPMN and Petri Nets. More information can be found at the webpage of the 2015 contest. Within this track we offer a subset of the tasks from the Process Model Matching Contest as OAEI track, by converting the process models to an ontological representation. By offering this track, we hope to gain insights in how far ontology matching systems are capable of solving the more specific problem of matching process models. This track is also motivated by the discussions at the end of the 2015 Ontology Matching workshop, where many participants showed their interest in such a track.

We converted the BPMN representation of the process models to a set of assertions (ABox) using the vocabulary defined in the BPMN 2.0 ontology (TBox). For that reason the resulting matching task is an instance matching task where each ABox is described bythe same TBox.


Th final results are now available at the results page!


The subset from the original contest that we have chosen is the University Admission dataset. It consist of process models that describe the process of university admission for different universities. Typical activities within that domain are Sending acceptance, Invite student for interview, or Wait for response. These examples illustrate one of the main differences to the ontology matching task: The labels are usually verb-object phrases that are sometimes extended with more words. Another important difference is obviously related to the existence of an execution order (i.e., the model is a complex sequence of activities) which can be understood as the counterpart to a type hierarchy.

The references alignment contains correspondences between instances of the class task as well as some correspondences between events. There are also some cases where tasks are matched on events (where it makes sense). The collection consists of 9 models ("Cologne", "Frankfurt", "FU_Berlin", "Hohenheim", "IIS_Erlangen", "Muenster", "Potsdam", "TU_Munich", "Wuerzburg"), for each pair exists an alignment in the gold standard. However, there is only an alignment named "Cologne-Frankfurt.rdf" and no alignment "Frankfurt-Cologne.rdf".

SEALS Support

This track runs in SEALS mode. i.e., the dataset is available as SEALS testsuite that can be executed via the SEALS client made available at the general OAEI webpage. This version is the ontology based version of the dataset.

July, 15th: Due to the hint from Muhammad Fahad we detected that the previously specified Version-ID was incorrect. In case you had problems accessing the testsuite, please try again using the ids presented below.

Anatomy Testsuite

Please feel free to write at any time a mail (contact below), if there are problems related to the testsuite!

In paralell, we will also offer the ontologies themselves for download (see above), which might be helpful for local tests. However, these files might differ slightly from the SEALS testsuite, which should be taken as reference.


If you have any questions or remarks, feel free to contact us.