Skip to content
About · editorial reference

About Formatory, an independent reference for formats and metadata

Formatory, published at udfr.org, explains how digital files are identified, described and kept usable. It covers file format signatures and identification, preservation-friendly formats, Dublin Core and the DCMI metadata terms, related vocabularies such as FOAF and SKOS, and the ISO 639-2 and ISO 3166-1 code lists that metadata records rely on.

Who the pages are written for

The audience is practical: catalogers deciding how to fill a dc:format field, archivists running an intake of mixed media, developers who need to know why a ZIP signature also opens an EPUB, and students meeting linked data for the first time. Each term page gives the official definition and URI first and then the usage advice around it.

How the sections fit together

The site has three layers. The reference section holds one page per term: the fifteen Dublin Core elements, the DCMI metadata terms that matter for files, the FOAF and SKOS properties that usually appear beside them, and the registry concepts used to describe formats, such as signatures, byte order, compression and disclosure. The guides take a task from start to finish, for example identifying an unknown file or choosing a format for long-term storage. The two complete code lists sit underneath both and can be downloaded as CSV.

The format registry history page traces how PRONOM, the Global Digital Format Registry and later unification efforts shaped the vocabulary still found in preservation systems today.

What the reference leaves out

Formatory does not host files, convert them or validate them against a specification, and it does not publish a full catalog of every format ever registered. Where a dedicated tool or registry does that work better, such as PRONOM for format records or JHOVE for validation, the relevant page names it and explains what it reports.

How the content is made

Pages are written and maintained by a small anonymous editorial team. Definitions are quoted from the published specifications (DCMI, FOAF, SKOS, ISO lists as published by their registration authorities); everything else is explanation in the team's own words. The code tables on the language code and country code pages are generated from the published lists so the numbers on the page always match the table. The identification tool runs entirely in the browser and reads only the first 32 bytes of a file.

Corrections

Specifications change and mistakes happen. Pages are reviewed against the current versions of the standards they describe, and the date shown on each page is the date of its last substantive revision.

This website is an independent editorial publication and is not operated by the California Digital Library.

Last reviewed