Skip to content

Apostille Documents

Apostille Documents are a future OpenETR domain workspace.

OpenETR can support Apostille Convention workflows as evidence, portability, and verification infrastructure. It should not be presented as the authority that issues Apostilles or decides their legal recognition.

Under the HCCH Apostille Convention, Apostilles are issued and verified by designated Competent Authorities. The HCCH electronic Apostille Programme, or e-APP, supports electronic issuance and verification, including e-Apostilles and e-Registers. OpenETR should complement those authority-led systems rather than replace them.

How OpenETR Could Fit

OpenETR could identify an apostilled document package as a Digital Artifact.

That package might include:

  • the public document;
  • the Apostille certificate;
  • e-Apostille data;
  • authority metadata;
  • registry lookup URL or identifier;
  • revocation, correction, or replacement references;
  • supporting notarial or certification material.

The digest of that package becomes the OpenETR object identity. OpenETR can then preserve an Evidence Graph concerning the object.

Competent Authorities As Recognized Attesters

In an OpenETR model, a Competent Authority should be treated as the issuer of a recognized attestation, not as the attestation itself.

That means:

  • the Digital Artifact is the document package being apostilled;
  • the Competent Authority is a designated issuer whose authority and key binding require verification, not necessarily a controller;
  • the Apostille authenticates the relevant public-document signature, signing capacity, and seal or stamp; OpenETR may separately bind its digital representation to a digest;
  • the recognition rule says that attestations from this authority, for this jurisdiction and document class, are accepted as Apostille evidence.

This separates technical verification from legal recognition:

Question Layer
Does the signature verify? Technical verification.
Is the issuer a known authority? Trust registry or authority metadata.
Is the authority competent for this document? Legal, jurisdictional, or governance rule.
Is the Apostille accepted by the relying party? Recognition outcome.

This lets OpenETR preserve digest-linked evidence and official authority references without implying a transfer of control. The public-document signer, Competent Authority, Anchor Publisher, and verifier may be different actors. Their signatures and statements must be evaluated separately.

Official Verification And Electronic Form

The recognition boundary operates within the Convention's obligations. The HCCH confirms that an e-Apostille cannot be refused simply because it is electronic. OpenETR adds an optional evidence facility, not another mandatory legalisation step. HCCH guidance.

A register lookup may confirm particular certificate fields without verifying every byte of a presented file. A verifier's signed observation is not the same evidence as an authority-signed response. A scan is a distinct artifact, and a QR code on paper does not prove that the paper matches the official digital record.

Candidate Evidence Graph Records

An Apostille Documents domain profile could define evidence records such as:

Evidence Graph Record Purpose
Anchor Record First OpenETR record for the apostilled document bundle.
Authority attestation Signed statement by, or linked to, a Competent Authority or recognized registry source.
Registry reference Link to an official e-Register or verification endpoint.
Verification event Evidence that a verifier checked the Apostille at a particular time.
Replacement event Link from a superseded Apostille package to a corrected or reissued one.
Revocation, warning, or invalidity notice Signed notice from an authority or recognized verifier.
Translation or legalization reference Link to related certified translations, legalization steps, or downstream recognition artifacts.

Where OpenETR Helps

OpenETR could make Apostille document workflows more portable by giving every apostilled package:

  • a durable digest-based identifier;
  • a QR code and durable link;
  • a retrievable original record, if stored;
  • an inspectable Evidence Graph;
  • independent signature and event verification;
  • links to official Competent Authority or registry verification sources.

This could be useful when apostilled documents circulate across email, portals, registries, courts, universities, immigration systems, commercial counterparties, and long-term archives.

Recognition Boundary

OpenETR should not claim:

  • to issue Apostilles;
  • to replace Competent Authorities;
  • to decide whether an Apostille is legally valid;
  • to force recognition by a Contracting Party;
  • to replace official e-Registers or e-Apostille certificates.

Instead, OpenETR can say:

Here is the controlled document bundle, its digest, its signed evidence graph, and its links to official authority or registry verification.

Legal recognition remains with the relevant authority, law, treaty framework, registry, relying institution, or verifier policy.

Domain Vocabulary

OpenETR Concept Apostille Documents Mapping
Digital Artifact Apostilled document bundle, e-Apostille package, notarized/certified document package, or related verification artifact.
Anchor Record Initial OpenETR record for the package digest.
Evidence Graph Linked evidence about authority, provenance, registry references, verification, replacement, or warnings.
Recognition layer Apostille Convention rules, Competent Authority practice, e-Register checks, local law, court or agency policy, and relying-party verification rules.

More to come.

For the policy framing and proposed consequential-state boundaries, see Apostille Records Need Consequential State. For the public-seal connection, see Electronic Seals And OpenETR.