Skip to content
Class · DCMI classes and encoding schemes

DCT MediaType class: definition, hierarchy and usage in records

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

A file format or physical medium.

dcterms:MediaType is the DCMI class defined as “a file format or physical medium”. That single sentence covers a lot of ground: a JPEG, a WAVE file, a reel of quarter-inch audio tape and a glass plate negative all qualify. The class exists so that format-related properties have something formal to point at, and so a validator can tell a format from, say, a file size.

Position in the DCMI class hierarchy

MediaType sits in the middle of a short chain:

Class Defined as Typical member
MediaTypeOrExtent a media type or extent anything valid for dcterms:format
MediaType a file format or physical medium “TIFF”, “VHS cassette”
FileFormat a digital resource format “TIFF 6.0”
PhysicalMedium a physical material or carrier “VHS cassette”

dcterms:format takes MediaTypeOrExtent as its range, which is why a single property can hold both “application/pdf” and “212 pages”. dcterms:medium takes PhysicalMedium, which is narrower. dcterms:FileFormat is the right type for anything that exists only as bits.

Physical and digital in one record

The value of having both branches under one class shows up in digitization work. A box of slides arrives, gets scanned, and the resulting record has to say two things: the original was a 35 mm color slide, and the surrogate is a TIFF. With MediaType as a common parent, both statements are well typed. The slide goes into dcterms:medium, the TIFF into dcterms:format, and nothing has to be squeezed into a free-text note. Queries benefit too: a request for every record whose original carrier was a slide works on dcterms:medium alone, without parsing descriptions that mention slides in passing or confusing a slide with a presentation file.

Born-digital material that arrived on a carrier is the reverse case. A thesis submitted on a CD-R in 2003 is a set of files, but knowing it was a CD-R matters: optical discs of that era are now a recognized preservation risk, and the carrier explains why some files may be unreadable. Format registries describe carriers in their own way; the media write type records whether a medium is write-once or rewritable.

Internet Media Types as members

Most digital MediaType values in practice come from the IANA registry, which DCMI identifies as the scheme dcterms:IMT. A value such as video/mp4 is a MediaType that belongs to the IMT list. Pairing the value with the scheme tells harvesters to treat it as a registered media type and not a phrase.

Physical media have no equivalent single registry. Libraries tend to use the RDA carrier type vocabulary (available from the Library of Congress at id.loc.gov), which supplies terms like “audiocassette” and “computer disc” with stable URIs. The RDA list is short (a few dozen carriers grouped by audio, computer, microform, projected image, video and unmediated material), which makes it a practical controlled list for dcterms:medium even in collections that do not otherwise follow RDA.

Mistakes seen in harvested records

The commonest is putting extent into dcterms:medium: “3 discs” is an extent, the carrier is “computer disc”. The second is recording a file extension as a media type, “.docx” where application/vnd.openxmlformats-officedocument.wordprocessingml.document was meant. The full string is long and unappealing, which is exactly why it gets abbreviated, and why extension-based values are worth normalizing before records are shared.

A smaller one, and easy to miss in review: declaring every format resource as dcterms:MediaType when dcterms:FileFormat was available. It is not wrong, since FileFormat is a subclass, but it throws away the distinction a query would need to separate digital formats from carriers. Typing each value with the most specific class available costs nothing at creation time.

Example in RDF

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
         xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
         xmlns:dcterms="http://purl.org/dc/terms/">
  <dcterms:MediaType rdf:about="https://example.org/media/cd-r">
    <rdfs:label>CD-R disc</rdfs:label>
  </dcterms:MediaType>
  <rdf:Description rdf:about="https://example.org/accessions/2003-17">
    <dcterms:medium rdf:resource="https://example.org/media/cd-r"/>
    <dcterms:format rdf:resource="https://example.org/formats/wave"/>
  </rdf:Description>
</rdf:RDF>

Questions about dcterms:MediaType

What is dcterms:MediaType?

It is the DCMI class defined as 'a file format or physical medium'. Its members are things like PDF, MP3 or a 35 mm slide, and it serves as the expected type of values for format-related properties in DCMI Metadata Terms.

Which classes sit above and below MediaType?

MediaType is a subclass of dcterms:MediaTypeOrExtent, which is the range of dcterms:format. Below it sit dcterms:FileFormat for digital formats and dcterms:PhysicalMedium for material carriers. Values of dcterms:format can therefore be file formats, physical media or extents, and the class tells them apart.

Is a MediaType the same as a MIME type?

A MIME type, more properly an Internet Media Type, is one possible member of the class. The class is wider: it also includes physical media such as videotape or paper, which have no MIME type at all.

Should I use dcterms:format or dcterms:medium?

dcterms:format is the general property for a resource's format, extent or carrier. dcterms:medium is narrower, it names the material or physical carrier, and its range is dcterms:PhysicalMedium. For a born-digital file, format is the usual choice.

Can a digitized object have two media types?

Yes, and it often should. The record of a digitized slide can name the original physical medium with dcterms:medium and the digital file format with dcterms:format, keeping the original and the surrogate distinct.

More from DCMI classes and encoding schemes

All 10 in this group