Since 2010, it is not necessary anymore to download the data set (it has always been better to get it on the web. The SEALS platform will provide the data sets. In the future, it is even planned that it will generate the data set on the fly.
The goal of the benchmark2 test library is to offer a set of tests which are wide in feature coverage, progressive and stable. It serves the purpose of evaluating the strength and weakness of matchers (by being progressive and wide coverage) and measuring the progress of matchers (by being stable and reusable over the years).
Apart from that, it is made of a set of 103 pairs of ontologies for which the participants have to return an alignment in the alignment format. These results are compared against reference alignments which are available from the beginning.
This year, we will use new systematically generated benchmarks, based on other ontologies than the bibliographic one. Participants can test their tools using the previous benchmark as well as a new generated test set, named Benchmark2. Both datasets are publicity available here and under the SEALS platform. However, the final evaluation will be based on a second newly generated benchmark, not available during the test period (we have already checked that results remain consistent across benchmarks).
The tests are systematically generated to as to start from some reference ontology and discarding a number of information in order to evaluate how the algorithm behave when this information is lacking.
Test numbering (almost) fully preserves the numbering of the first EON contest.
The table below summarize what has been retracted from the reference ontology. There are here 6 categories of alteration:
| # | Name | Com | Hier | Inst | Prop | Class | Comment | |
| 101 | 0 | 0 | 0 | 0 | 0 | 0 | Reference alignment | |
| 201 | R | 0 | 0 | 0 | 0 | 0 | No names | |
| 202 | R | N | 0 | 0 | 0 | 0 | No names, no comments | |
| 221 | 0 | 0 | N | 0 | 0 | 0 | No specialisation | |
| 222 | 0 | 0 | F | 0 | 0 | 0 | Flatenned hierarchy | |
| 223 | 0 | 0 | E | 0 | 0 | 0 | Expanded hierarchy | |
| 224 | 0 | 0 | 0 | N | 0 | 0 | No instance | |
| 225 | 0 | 0 | 0 | 0 | R | 0 | No restrictions | |
| 228 | 0 | 0 | 0 | 0 | N | 0 | No properties | |
| 232 | 0 | 0 | N | N | 0 | 0 | ||
| 233 | 0 | 0 | N | 0 | N | 0 | ||
| 236 | 0 | 0 | 0 | N | N | 0 | ||
| 237 | 0 | 0 | F | N | 0 | 0 | ||
| 238 | 0 | 0 | E | N | 0 | 0 | ||
| 239 | 0 | 0 | F | 0 | N | 0 | ||
| 240 | 0 | 0 | E | 0 | N | 0 | ||
| 241 | 0 | 0 | N | N | N | 0 | ||
| 246 | 0 | 0 | F | N | N | 0 | ||
| 247 | 0 | 0 | E | N | N | 0 | ||
| 248 | N | N | N | 0 | 0 | 0 | ||
| 249 | N | N | 0 | N | 0 | 0 | ||
| 250 | N | N | 0 | 0 | N | 0 | ||
| 251 | N | N | F | 0 | 0 | 0 | ||
| 252 | N | N | E | 0 | 0 | 0 | ||
| 253 | N | N | N | N | 0 | 0 | ||
| 254 | N | N | N | 0 | N | 0 | ||
| 257 | N | N | 0 | N | N | 0 | ||
| 258 | N | N | F | N | 0 | 0 | ||
| 259 | N | N | E | N | 0 | 0 | ||
| 260 | N | N | F | 0 | N | 0 | ||
| 261 | N | N | E | 0 | N | 0 | ||
| 262 | N | N | N | N | N | 0 | ||
| 265 | N | N | F | N | N | 0 | ||
| 266 | N | N | E | N | N | 0 | ||
One can observe that a subset of the modifications from original benchmark has been applied for generating the benchmark2 dataset. Some tests have been discarded while other ones have been added:
Below are provided the set of tests with expected alignments in the Alignment format described here. Each ontology is to be aligned with the reference ontology (i.e., that of test #101).
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.
There is some chance that the final test be improved by adding entity expansion and reduction. It is also possible that there will be a lot of more instances in each ontology.
This test compares the ontology to itself.
Ontology : [RDF/XML]
[HTML]
Alignment : [RDF/XML]
[HTML]
Each label or identifier is replaced by a random one.
Ontology : [RDF/XML]
[HTML]
Alignment : [RDF/XML]
[HTML]
All subclass assertions to named classes are suppressed.
Ontology : [RD/XML]
[HTML]
Alignment : [RDF/XML]
[HTML]
(variation: compile inheritance)
A hierarchy still exists but has been strictly reduced.
Ontology : [RDF/XML]
[HTML]
Alignment : [RDF/XML]
[HTML]
The alignment here contains relations which are not "=" but "<".
Numerous intermediate classes are introduced within the hierarchy.
Ontology : [RDF/XML]
[HTML]
Alignment : [RDF/XML]
[HTML]
All individuals have been suppressed from the ontology.
Ontology : [RDF/XML]
[HTML]
Alignment : [RDF/XML]
[HTML]
All local restrictions on properties have been suppressed from the ontology.
Ontology : [RDF/XML]
[HTML]
Alignment : [RDF/XML]
[HTML]
(variation: no property nor global restrictions on properties)
In this test all datatypes are converted to xsd:string.
Not available in this test
(Measurable) values are expressed in different datatypes.
Not available in this test
Properties and relations between objects have been completely suppressed.
Ontology : [RDF/XML]
[HTML]
Alignment : [RDF/XML]
[HTML]
(variation: leave the properties in instances)
Some classes have become instances.
Not available in this test.
Ontology : [RDF/XML]
[HTML]
Alignment : [RDF/XML]
[HTML]
Ontology : [RDF/XML]
[HTML]
Alignment : [RDF/XML]
[HTML]
Ontology : [RDF/XML]
[HTML]
Alignment : [RDF/XML]
[HTML]
Ontology : [RDF/XML]
[HTML]
Alignment : [RDF/XML]
[HTML]
Ontology : [RDF/XML]
[HTML]
Alignment : [RDF/XML]
[HTML]
Ontology : [RDF/XML]
[HTML]
Alignment : [RDF/XML]
[HTML]
Ontology : [RDF/XML]
[HTML]
Alignment : [RDF/XML]
[HTML]
Ontology : [RDF/XML]
[HTML]
Alignment : [RDF/XML]
[HTML]
Ontology : [RDF/XML]
[HTML]
Alignment : [RDF/XML]
[HTML]
Ontology : [RDF/XML]
[HTML]
Alignment : [RDF/XML]
[HTML]
Ontology : [RDF/XML]
[HTML]
Alignment : [RDF/XML]
[HTML]
Ontology : [RDF/XML]
[HTML]
Alignment : [RDF/XML]
[HTML]
Ontology : [RDF/XML]
[HTML]
Alignment : [RDF/XML]
[HTML]
Ontology : [RDF/XML]
[HTML]
Alignment : [RDF/XML]
[HTML]
Ontology : [RDF/XML]
[HTML]
Alignment : [RDF/XML]
[HTML]
Ontology : [RDF/XML]
[HTML]
Alignment : [RDF/XML]
[HTML]
Ontology : [RDF/XML]
[HTML]
Alignment : [RDF/XML]
[HTML]
Ontology : [RDF/XML]
[HTML]
Alignment : [RDF/XML]
[HTML]
Ontology : [RDF/XML]
[HTML]
Alignment : [RDF/XML]
[HTML]
Ontology : [RDF/XML]
[HTML]
Alignment : [RDF/XML]
[HTML]
Ontology : [RDF/XML]
[HTML]
Alignment : [RDF/XML]
[HTML]
Ontology : [RDF/XML]
[HTML]
Alignment : [RDF/XML]
[HTML]
Ontology : [RDF/XML]
[HTML]
Alignment : [RDF/XML]
[HTML]
Ontology : [RDF/XML]
[HTML]
Alignment : [RDF/XML]
[HTML]
Ontology : [RDF/XML]
[HTML]
Alignment : [RDF/XML]
[HTML]
The release notes of the test versions can be found here.
The test set is made of a set of directories (one per test) containing an ontology (onto.owl) in OWL. Participants must match each of these ontologies with the ontology found in 101/onto.owl and output the resulting alignment, in the alignment format, in a file participant.rdf in the same directory (participant is replaced by the name of the system: no more than 8 alphanumeric characters, lowercase).
The test set also contains the reference alignments against which the results will be evaluated. It is, of course, forbidden to use any for there results for performing the matching task.
The resulting alignments in the same directory structure can be zipped (please, zipped) and sent to the organisers.
The schedule is that of http://oaei.ontologymatching.org/2011/.
A zip file contains all the data about the benchmark2 dataset. That is:
We would like to find a simple converter from OWL/XML/RDF to N3 (and maybe RDFS).
You can use the Alignment API for manipulating and generating your alignments (in particular for computing evaluation of your results).
Contact address is Cassia : Trojahn # inrialpes : fr