Skip to content
Property · Format description concepts

Reference purpose: why a format record cites each of its sources

Published Formatory editorial team

Reference purpose is a property that states the role a cited document or resource plays in a descriptive record, such as authoritative specification, secondary description or source of identification evidence.

Registries attach it to each documentary reference so that readers can separate the defining specification from commentary, tools and test material.

Most people know the phrase “for reference purposes only” as a disclaimer on a document. In a format registry, the purpose of a reference is something more specific and more useful: a label on each cited source that tells the reader why that source is there.

A format record for WAVE audio might cite the 1991 Microsoft and IBM multimedia specification, a later Microsoft document on extensible formats, a widely read web tutorial, a PRONOM entry and a folder of sample files. All five are references. Only the first two define the format, and only the samples help test a signature. Without a purpose label, they appear as one undifferentiated list.

Common purposes

Vocabularies vary, yet the same distinctions keep turning up:

  1. Specification, the document that defines the format. Formal standards, vendor specifications and RFCs belong here.
  2. Description, a secondary account: encyclopedia articles, books, technical notes, other registries’ records.
  3. Identification evidence, the source of a magic number or other signature, sometimes a specification section, sometimes observed sample files.
  4. Test data, sample files or test suites, such as conformance files published alongside a standard.
  5. Implementation, software that reads or writes the format, cited when its behavior defines details the specification leaves open.
  6. Related standard, a document the format depends on, for example the compression standard used inside a container.

The list is not exhaustive. Some registries also separate history (sources about how a format came about) and risk (assessments of how sustainable a format is), which become useful once a record has accumulated a dozen citations.

Each category deserves different trust. A specification is authoritative about what files should look like; implementations are authoritative about what files actually look like in the wild, and the two often disagree.

When there is no specification

Some formats have no public specification at all, and many have only a partial disclosure. In those cases references do most of the documentary work: reverse-engineering notes, the source code of an open-source reader, mailing-list posts by developers. Labeling them honestly matters, since a reverse-engineered description cited as if it were the specification invites later readers to treat guesses as rules.

A short note next to such a reference, saying which version of the format it was tested against and how many sample files supported it, costs the cataloger a minute and saves later readers from overreading it.

The same logic applies to images in a record. A structure diagram drawn from the specification is a kind of reference, and its image purpose value plays the same role for pictures that reference purpose plays for documents.

References change over time

Specifications get revised, URLs move and vendor documentation disappears. A reference record that includes the title, publisher, edition or version, and the date it was consulted survives these changes better than a bare link. Some registries also record when a claim based on a reference took effect, which connects reference purpose to the effective claim date of the statement it supports.

A good habit, when a source exists only online, is to deposit a copy or cite a persistent identifier. A DOI, a standards body’s document number such as RFC 2083 for PNG 1.0, or an ISO reference like ISO/IEC 15948 for PNG gives a reader something to look up even after the original URL is gone. The file format identification guide explains how specification references feed signature work, and the vocabulary index lists related properties.

Example in RDF

<format rdf:about="https://example.org/formats/wave-pcm">
  <name>Waveform Audio File Format (PCM)</name>
  <reference>
    <title>Multimedia Programming Interface and Data Specifications 1.0</title>
    <referencePurpose>Specification</referencePurpose>
    <date>1991-08</date>
  </reference>
  <reference>
    <title>Sample WAV files for signature testing</title>
    <referencePurpose>Test data</referencePurpose>
  </reference>
</format>

Questions about Reference purpose

What is a reference purpose?

It is a label on a cited source that says why the record cites it. One reference may be the format's defining specification, another a tutorial, another the place a file signature was taken from, another a set of sample files.

Why does the purpose of a reference matter?

A reader checking a technical claim needs the authoritative source, not a blog post that repeats it. Labeling purposes lets a record carry many references while making clear which one decides a question about the format.

What counts as an authoritative specification?

The document published by the body that controls the format: a formal standard (ISO, IETF, ITU), a vendor's own specification, or a community-maintained specification with a named editor. Third-party descriptions are secondary, however detailed.

What if no specification exists?

Then the record says so and cites what does exist: reverse-engineering notes, the source code of an open implementation, or sample files. These references should carry purposes that make clear they are not a specification.

Can one reference have several purposes?

Yes. A standard can be both the defining specification and the source of a file signature. A repeatable purpose value handles this better than duplicating the reference with a different label.

More from Format description concepts

All 16 in this group