/
Technical Glossary

Technical Glossary

The Technical Glossary defines implementation-specific terminology used by the EIDR Registry, APIs, XML schemas, and identifier framework.

Unlike the EIDR Glossary, which explains concepts used throughout the Reference Library, this glossary focuses on the internal architecture, data structures, identifier formats, and processing behavior of the Registry.

This reference is intended primarily for software developers, systems integrators, solution architects, and others building applications that interact with EIDR.

Terms are listed alphabetically.

B

Base Object Data

The collection of metadata fields common to all EIDR Content records.

Examples include:

  • Resource Name

  • Alternate Resource Names

  • Release Date

  • Original Language

  • Country of Origin

  • Credits

  • Associated Organizations

  • Alternate IDs

Many Base Object Data fields participate in metadata inheritance and deduplication.

Base64URL Representation

A URL-safe encoding of the Compact Binary form of an EIDR identifier.

Base64URL representations are used when identifiers must be embedded in URLs, filenames, or other environments where the standard DOI representation is not suitable.

Batch Mode

A processing mode that submits multiple Registry operations within a single transaction.

Each request is processed independently and returns its own result.

C

Canonical Form

The standard DOI representation of an EIDR identifier.

Example:

10.5240/XXXX-XXXX-XXXX-XXXX-XXXX-C

The canonical form should be used when exchanging identifiers with the Registry.

Check Character

The final character of an EIDR identifier.

The check character is calculated using the ISO 7064 Mod 37,36 algorithm and is used to detect transcription and formatting errors.

Compact Binary

A compact 96-bit binary representation of an EIDR identifier.

Compact Binary is intended for storage and transmission in systems where space efficiency is important.

D

DOI Kernel

A compact DOI representation containing a subset of identifier metadata.

The DOI Kernel is used by DOI resolution services and other DOI-based applications.

DOI Proxy

The DOI resolution service used to resolve EIDR identifiers to Registry metadata.

E

EIDR-F

A filename-safe representation of an EIDR Content ID.

The EIDR-F format replaces the DOI prefix with a shorter representation suitable for file naming while preserving the identifier value.

EIDR-S

A URN-based representation of an EIDR identifier.

Used by systems that exchange identifiers using URN syntax rather than DOI syntax.

EIDR-X

An extension of EIDR-S that permits additional domain-specific suffixes.

The additional suffixes are governed by the implementing organization rather than by EIDR.

N

Namespace

A collection of identifiers managed under a common DOI prefix.

EIDR maintains separate namespaces for Content, Parties, Users, and Video Services.

S

Structural Type

An internal classification that identifies the broad category of an EIDR record.

Structural Types distinguish conceptual works, creative versions, technical representations, and physical objects within the Registry's data model.

Users do need to specify Structural Type when creating a submission. It is currently exposed in the user interface and must be selected, but this requirement is temporary and will be addressed in a future update.

T

Token

A transaction identifier returned by the Registry for asynchronous operations.

Tokens allow clients to retrieve processing results after submission.

U

URN

A Uniform Resource Name representation of an EIDR identifier defined by RFC 7972.

URN representations are accepted by the DOI resolution service but are not accepted by the EIDR API.