specs

specs copied to clipboard

Reconciliation candidates returned by services can contain a "matched" attribute, which indicates whether the service predicts that the entity matches the query.

At the moment, we do not specify anything about this attribute. For instance, it is possible for a candidate to be marked as "matched" even if it is not the highest-scoring one. One can also have multiple reconciliation candidates with "matched": true. https://reconciliation-api.github.io/specs/latest/#reconciliation-query-responses

A referee from the Ontology Matching 2020 workshop mentions that it is important for the OAEI community to support matching one tabular entry to multiple entities to the knowledge base (perhaps when it contains duplicates?), so perhaps it is actually useful not to forbid returning multiple "matched": true.

Ok, maybe that's a realistic case. But can we say in the spec that "usually..." then include the proposed rules in #58