Skip to content
Property · DCMI Metadata Terms: properties

dct:format usage: media types, extent and medium in DCMI Terms

Published Formatory editorial team
http://purl.org/dc/terms/format

The file format, physical medium, or dimensions of the resource.

Recommended practice is to use a controlled vocabulary where available. For example, for file formats one could use the list of Internet Media Types [MIME]. Examples of dimensions include size and duration.

A file’s form, in the sense of how its bytes are encoded or what it is physically carried on, is what this property records. dct:format (written dcterms:format in much library documentation) is the DCMI Metadata Terms version of the format element, with the same definition as dc:format and one important addition, a declared range.

The MediaTypeOrExtent range

The range is dcterms:MediaTypeOrExtent, a class that groups two narrower ones: dcterms:MediaType for file formats and physical media, and dcterms:Extent for size or duration. dcterms:FileFormat is in turn a sub-class of MediaType, meant specifically for digital file formats.

What the range changes in practice is the shape of the value. In the original element set a string such as application/pdf is normal. With a declared range, the value is expected to be a resource, so linked-data records use a URI: an IANA media type page, an entry in a format registry or a concept from an authority list. A literal is still common, and some validators accept it, but it does not say what kind of thing the string names.

The choice has a cost either way. URIs make records heavier to write by hand and depend on someone keeping the target list online. Literals are easy to type and easy to get wrong: image/jpg, JPEG, jpeg and JPG image all appear in real catalogs for one format. Collections that cannot adopt URIs throughout often get most of the benefit from a pick list of approved media type strings in the cataloging form.

The dcterms:IMT encoding scheme sits between the two approaches. It marks a literal or a resource as a member of the Internet Media Types list, which is enough for processors that know the scheme.

Extent and medium

DCMI Metadata Terms splits two parts of the old definition into sub-properties of dcterms:format:

Property Holds Example value
dcterms:extent size or duration 212 pages; 00:48:10; 3.2 GB
dcterms:medium material or physical carrier oil on canvas; LTO-7 tape

Using them leaves dcterms:format for what most users mean by format: the encoding of a file. A record with all three properties is easier to filter and to crosswalk than one with three different kinds of value packed into the same field. dcterms:medium carries a domain restriction that catches people out, and its own page covers the inference it triggers.

dct:format in DCAT catalogs

The W3C Data Catalog Vocabulary is where most developers meet the dct: prefix. DCAT reuses dct:format on distributions, the downloadable or accessible forms of a dataset, and adds dcat:mediaType, defined as a sub-property of dct:format and restricted to IANA media types.

The division of labor is straightforward. A CSV file gets dcat:mediaType pointing to the IANA entry for text/csv. A format with no registered media type, such as many GIS or domain-specific formats, gets dct:format with a URI from a controlled list; European portals use the EU Publications Office file type authority table for this. Supplying both, as the example does, costs little and serves harvesters that read only one of them.

Version and profile

Neither a media type nor a broad file type entry says which version of a format a file uses. text/csv does not say which delimiter or encoding was chosen, and application/pdf covers PDF/A, PDF/X and every PDF version in between. For preservation work that gap matters. Format registries assign identifiers at version level, and identification tools such as DROID or Siegfried can report them; the format identification guide covers how to obtain and record them. Where a resource exists in several encodings, dcterms:isFormatOf links each derivative back to the version it was made from, so that every copy carries its own accurate dct:format.

Example in RDF

@prefix dct: <http://purl.org/dc/terms/> .
@prefix dcat: <http://www.w3.org/ns/dcat#> .

<https://example.org/data/air-quality/distribution/csv>
    a dcat:Distribution ;
    dct:format <http://publications.europa.eu/resource/authority/file-type/CSV> ;
    dcat:mediaType <https://www.iana.org/assignments/media-types/text/csv> ;
    dcat:byteSize 482113 .

Questions about dcterms:format

What is dct:format?

dct:format is the usual prefixed form of dcterms:format in DCMI Metadata Terms. It records the file format, physical medium or dimensions of a resource and is a sub-property of the original dc:format element.

What is the range of dcterms:format?

The range is dcterms:MediaTypeOrExtent, a class covering media types and extents. In linked-data terms the value is expected to be a resource, typically identified by a URI, and not a bare text string.

How does dcat:mediaType relate to dct:format?

In DCAT, dcat:mediaType is defined as a sub-property of dct:format and is meant for IANA media types only. dct:format remains available for formats without a media type, often taken from a controlled list such as the EU file type authority table.

Should size and duration go in dcterms:format?

They can, since the definition includes dimensions, but dcterms:extent is the more precise choice. It is a sub-property of dcterms:format for the size or duration of the resource, such as a page count, a running time or a file size.

Can dct:format hold a file extension like .xlsx?

It can hold one as a literal in loose practice, but extensions are not a controlled vocabulary and do not fit the declared range well. A media type URI or an entry from a format registry identifies the format far more reliably.

More from DCMI Metadata Terms: properties

All 13 in this group