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.

Version
v3 · 2026-09-28 · History
Domain-specific #
425
Domain group
Applied Sciences & Engineering
Origin domain
Computer Science & Software Engineering
Subdomains
Information Technology, Resource Description → Computer Science & Software Engineering

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.

How would you explain it like I'm…

The What-Form Sticker

A story can be a paper book, a picture on a tablet, or a voice on a tape. It is the same story in different packages. A format relation is a little label that says which package this copy comes in, so nobody has to open it to guess.

File Type Label

A computer file holds something, like a report or a photo, and it is stored in a certain form, such as a PDF or a TIFF picture. A Format Relation is a piece of information about the file that clearly says which form it is in. That way, the computer doesn't have to guess from the end of the file name or peek inside the file. One report might exist in several forms, one for editing, one for printing, and one for the web, and each can be labeled.

Recorded Encoding Metadata

A format relation is a piece of metadata linking a resource to the encoding or file format it exists in, such as 'this photo is a TIFF at 600 dpi.' Its key idea is separating identity (what the work is) from encoding (the form it currently takes). Instead of guessing the type from a filename ending like .pdf or by peeking at the bytes, the format is recorded explicitly as its own property that can be searched. That lets systems decide how to display a file, which processing path to send it down, and which old formats need converting before they become unreadable. One work can have several formats recorded, like DOCX for editing, PDF/A for archiving, and HTML for the web.

 

In information science, a format relation binds a resource to the medium, encoding, or file format in which it is materialized, e.g., 'this dataset is CSV with UTF-8 encoding.' Structurally it enforces a distinction between a resource's identity and its encoding, and records the encoding as a first-class, queryable property rather than something inferred from filename extensions or content sniffing. Standard vocabularies implement it: Dublin Core's dc:format, schema.org's encodingFormat, RDA carrier types in library cataloging, and PRONOM identifiers and IANA MIME types in digital preservation. This supports three operations without re-parsing the resource: rendering decisions (HTML for a screen reader, PDF for printing), ingestion routing (branching a pipeline by type), and preservation planning (flagging obsolescence risk and triggering migration). Because one work can have multiple manifestations, the relation can be recorded once per format. Without it, these tasks fall back on brittle heuristics; with it, they become reliable metadata queries.

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 — includesDistributionFormDOMAIN

Current abstraction Format Relation Domain-specific

Parents (2) — outgoing typed relations

  • 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) — abstractions linked here by typed relations

  • Distribution Form Domain-specific includes 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

  • Format Relation → is a kind of Relation

Neighborhood in Abstraction Space

Format Relation sits in a moderately populated region (52nd percentile for distinctiveness): it has near-neighbors but no dense thicket of look-alikes.

Family — Digital Resource Formats & Metadata (7 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-10-25