Skip to content

Format Relation

Bind a resource to the encoding it is materialized in as an explicit, queryable metadata field drawn from a controlled registry, so rendering, routing, and preservation read off the recorded format rather than re-parsing the bytes.

Core Idea

A metadata link binding a resource to the encoding, medium, or file format in which it is materialized — "this resource is a PDF," "this dataset is a UTF-8 CSV." Its structural commitment is separating a resource's identity (what the work is) from its encoding (the form it currently takes), naming the encoding as an explicit, queryable property drawn from a controlled registry rather than sniffing bytes or filename suffixes. Operationalized in Dublin Core dc:format, schema.org encodingFormat, PRONOM, and MIME types.

Scope of Application

Turns up wherever a resource is catalogued and its encoding must be recorded as an explicit, queryable property separate from its identity.

  • Library and bibliographic metadata — Dublin Core dc:format, MARC 856, RDA carrier vocabularies, FRBR layers.
  • Dataset management — DataCite, CKAN, Zenodo recording per-file format identifiers for ingestion planning.
  • Digital preservation — PRONOM and JHOVE identification feeding migration and obsolescence monitoring.
  • Document governance — PDF/A for preservation, HTML for web, DOCX for drafting, as manifestations of one work.
  • Web content negotiation — HTTP Accept/Content-Type operating the relation at request time.

Clarity

Naming the relation forces the separation a catalog most needs and most often blurs: a resource's identity versus its encoding. Once format is a recorded property rather than read off a suffix, one work can carry several manifestations without any being mistaken for the work. It relocates rendering, ingestion routing, and preservation planning from fragile heuristics to reliable metadata queries.

Manages Complexity

A repository's bewildering spread of encodings collapses, for operational purposes, to the cardinality of a registry — a closed set of identifiers the pipeline already knows how to branch on. The encoding stops being inferred anew each time and becomes a value read once and queried thereafter. Rendering, routing, and preservation disposition all read off one field per manifestation, deterministically, instead of re-parsing bytes.

Abstract Reasoning

The relation licenses a diagnostic reading operational consequences off the recorded format value and preferring the asserted format to the inferred one, an interventionist move branching pipelines on the field and triggering preservation from registry membership, and boundary-drawing separating identity from encoding and the recording-of-encoding from the encoding machinery itself.

Knowledge Transfer

As a metadata field convention rather than a mechanism, the format relation transfers as the same convention across resource-cataloging sub-areas — the identity/encoding separation, controlled-vocabulary discipline, prefer-asserted diagnostic, and three enabled operations carry without translation across library metadata, dataset management, preservation, and web negotiation, doing identical work in each. Beyond cataloging the substrate-independent kernel is carried by the parents form_and_content, representation, encoding_and_decoding, and serialization; invoking "format relation" off-catalog collapses into that general distinction, so the convention stays home.

Relationships to Other Abstractions

Local relationship map for Format RelationParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.Format RelationDOMAINPrime abstraction: Form and Content — is a decomposition ofForm and ContentPRIMEPrime abstraction: Relation — is a kind ofRelationPRIMEDomain-specific abstraction: Distribution Form — is part ofDistributionFormDOMAIN

Current abstraction Format Relation Domain-specific

Parents (2) — more general patterns this builds on

  • Format Relation is a kind of Relation Prime

    Format Relation is a binary Relation specialized to a logical resource and one controlled identifier for the form in which it is realized.

  • Format Relation is a decomposition of Form and Content Prime

    Removing catalog registries from a format relation leaves the distinction between one logical content and the concrete forms that realize it.

Children (1) — more specific cases that build on this

  • Distribution Form Domain-specific is part of Format Relation

    A distribution-form record contains a format relation binding the logical resource to the media type or controlled format in which that form is made.

Hierarchy paths (2) — routes to 2 parentless roots

Neighborhood in Abstraction Space

Format Relation sits in a crowded region of the domain-specific corpus (31st percentile for distinctiveness): several abstractions share nearly its structure, so a description that fits it tends to fit its neighbors too.

Family — Unclustered & Miscellaneous (309 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-07-12