Identity and external ID matching
Support reliable cross-system subject matching while preserving unresolved identities, accountable decisions and reversible corrections.
Bundle → Layer → Finding → Questions Filled
2 bundles · 3 layers · 4 findings · 11 questions
Identifiers This bundle describes qualified identifiers and their subject bindings.
Identifier binding
This layer records the scope and status of one identifier binding.
Qualified identifier
This finding distinguishes confirmed bindings from unresolved or colliding identifiers.
- Which scheme and issuer qualify the identifier in this binding?
- Does this binding record a confirmed alias, an unresolved subject association or an identifier collision?
Resolution This bundle describes matching decisions and corrections to subject mappings.
Same-as assertion
This layer records evidence and decisions about a proposed subject match.
Match evidence
This finding records the basis and status of one identity claim.
- What evidence supports this claim that the referenced identifiers denote one subject?
- Does this match claim rely only on a name or email address?
- What decision status and decision authority are recorded for this identity claim?
Merge and split
This layer preserves accountable merge and split decisions with their correction obligations.
Reversible merge
This finding records one merge and the basis for reversing its mappings.
- Which records, decision time and supporting evidence are recorded for this merge?
- Which preserved history and reversal policy apply to this merge?
- Which downstream records are identified as affected by this merge?
Split decision
This finding records the resulting identities and correction obligations of one split.
- Which resulting subject identities does this split decision establish or restore?
- Which identifiers does this split decision assign to each resulting subject or retain as unresolved?
- Which downstream corrections, responsible roles and completion statuses are recorded for this split?
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise contract
- Entry kind
- contract
- Domain
- EnterpriseXCT
- Industry
- Cross-industry
- Tags
- EM-XCT-01W0contractIdentifierBindingIdentityAssertionIdentityResolution
What it is Filled
A shared contract for identifiers, aliases, same-as claims, merge/split and reversible mappings.
Why it exists Filled
Support reliable cross-system subject matching while preserving unresolved identities, accountable decisions and reversible corrections.
Distinguishing features Filled
- An identifier is qualified by its scheme and issuer, so identical strings can denote different subjects.
- A same-as claim carries evidence and status without silently overwriting either source record.
- Separate provisional subject records remain valid until sufficient evidence supports an authorized identity decision.
- An email match or a name match alone is not enough to merge identities.
- Every merge preserves the history needed to reverse mappings and identify downstream corrections.
- Strict subject identity is distinct from a mapping between concepts, and a contested claim does not establish equivalence.
What robots and AI may and may not do Filled
Must not
- Merge person records by name alone.
- Merge records on an email address match without further evidence.
- Treat an identifier without scheme and issuer as globally unique.
- Merge records in a way that cannot be reversed.
- Resolve a contested match silently without recording who decided.
- Publish a contested identity claim as established equivalence.
- Treat a concept mapping as proof that two subject records identify the same entity.
Only with a human decision
- A responsible human must approve merges of records concerning people.
- A responsible human must resolve contested identity matches.
- A responsible human must approve reversing a merge that downstream systems already rely on.
May
- Propose same-as links with the evidence that supports them.
- Preserve separate provisional subject records while identity matching remains unresolved.
- Keep colliding identifiers in a contested state until resolved.
- Record supported aliases for one subject across source systems.
- Reverse a merge within delegated authority using its recorded history when no human approval condition applies.
Moral aspects Filled
- Wrong merges can attach one person's data, history or liability to another person.
- Linking identities across systems increases surveillance and profiling risk and must stay within purpose.
Who is affected
- People whose records are linked or merged
- Data stewards of source systems
- Users relying on merged records
Owners Filled
Steward
An enterprise identity data steward is accountable for operational matching records and coordinates decisions with the responsible source data owners.
Master systems
- An identity resolution registry maintains matching claims and decision history.
- A master data management system maintains governed subject mappings.
- Source systems of record maintain their issued identifiers and subject records.
- A data governance workflow system maintains approvals and correction responsibilities.
Links to other meta-models Filled
references
- WM-XCT-011 - conceptual-candidate
- WM-XCT-036 - conceptual-candidate
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- An identifier is qualified by scheme, issuer and value.
- An identity assertion has its own identifier and refers to the bindings it links.
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition required Filled
- An identity assertion lists qualified identifiers, evidence and a decision status.
- A foreign key or deduplication result alone does not establish a supported identity assertion.
Capabilities and actions required Filled
- Links across systems can be traversed without forcing a single master record.
- Erroneous merges can be corrected using preserved history and explicit split decisions.
Hazards and failure modes required Filled
- Identifiers used without scheme and issuer can create identity collisions.
- Incorrect merges can spread one subject's data to another.
- Excessive linking can expose personal data beyond its authorized purpose.
Standards and interfaces optional Filled
- The World Wide Web Consortium OWL owl:sameAs property expresses strict identity and must not encode unresolved or contested matches as established equivalence.
- The World Wide Web Consortium SKOS mapping properties relate concepts and do not establish identity between person or other subject records.
- The ISO/IEC 11179 series issued jointly by the International Organization for Standardization and the International Electrotechnical Commission addresses metadata registries and identification of data elements.
- The Internet Engineering Task Force RFC 3986 defines URI syntax for identifier representation.
Context of use required Filled
- Matching applies when records about potentially shared subjects arrive from several systems.
- Identity linking involving people remains subject to applicable data protection requirements.
Sources Filled
- Current Vercy protocol/MMAS/whole-object and the published WM-XCT
- W3C PROV/SKOS/SHACL/ODRL where applicable
- Practice of source connectors, versioned schemas and policy enforcement
- W3C OWL 2 Web Ontology Language: Structural Specification and Functional-Style Syntax - Checked live (HTTP 200) on 2026-10-07.
- W3C SKOS Simple Knowledge Organization System Reference - Checked live (HTTP 200) on 2026-10-07.
Open questions
- What evidence permits a merge?
- How to distinguish a collision from an alias?
- How to undo an erroneous merge?
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-xct-01/brief.json, ver-cy/world-models/card-supplements/em-xct-01.json
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.