DataTerminology.comNEW
Also known as: skos:exactMatch
A mapping indicating two concepts are equivalent in meaning.
DESCRIPTION
Exact Match expresses strong equivalence between concepts across different vocabularies, implying they are interchangeable for most retrieval and integration purposes. In SKOS, skos:exactMatch is a mapping property often used in crosswalks and federated catalogs. It should be applied cautiously, with evidence and governance, because overuse can degrade precision and recall. Exact matches typically align identifiers, labels, scope notes, and usage contexts.
ALTERNATIVE DEFINITIONS
W3C SKOS Primer
skos:exactMatch indicates a high degree of confidence that two concepts can be used interchangeably.
Stresses interchangeability and high confidence in equivalence across schemes.
W3C SKOS Reference
skos:exactMatch is used to link two concepts that can be used interchangeably across different concept schemes.
Highlights inter-scheme equivalence rather than hierarchical relations.
RELATED TERMS
Mapping Relation Simple Knowledge Organization System Knowledge Representation Value Set Cross-Reference Lists Alignment Thesaurus RDF Equivalence
COMPETING TERMS
KNOWLEDGE AREAS
Semantic & Knowledge Modeling Metadata Management
TARGET AUDIENCE
Data Steward Information Analyst Data Modeler
EXTERNAL SOURCES
- Wikipedia - Simple Knowledge Organization System
- W3C - Primer overview on exactMatch usage
- W3C - Reference defining SKOS mapping properties
TOP QUESTIONS
When should Exact Match be used instead of Close Match?
Use Exact Match only for true conceptual equivalence across schemes. If contexts or scope differ, prefer Close Match to avoid overstating similarity.
Category: Requirements
What is the biggest misunderstanding about Exact Match?
Many treat it as a convenient shortcut; it requires evidence of interchangeability. Incorrect exact matches reduce retrieval quality.
Category: Misunderstanding
How is Exact Match validated in practice?
Review labels, scope notes, definitions, and usage contexts. Peer review and governance workflows ensure consistency.
Category: Management
What are common mistakes with Exact Match in data catalogs?
Equating near-synonyms or different granularities. Overuse leads to false positives in search.
Category: Mistakes
What risks arise from misusing Exact Match?
User confusion, inaccurate analytics, and loss of precision. Downstream systems propagate incorrect equivalences.
Category: Risk
How does Exact Match affect knowledge graphs?
It merges concept identities across graphs, strengthening entity resolution. Accurate matches improve connectivity and insights.
Category: Impact
Is Exact Match symmetric and transitive?
Exact Match is symmetric, but care with transitive implications is needed across differing schemes to avoid unwarranted cascades.
Category: Opinion
What documentation should accompany Exact Match decisions?
Record provenance, rationale, reviewers, and date. Link to evidence such as definitions and scope notes.
Category: Best practices
Which standards define Exact Match semantics?
W3C SKOS specifies exactMatch as an inter-scheme equivalence property, widely adopted in linked data.
Category: Standard