Skip to content
Property · DCMI Metadata Terms: properties

dcterms:medium: recording the material or carrier of a resource

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

The material or physical carrier of the resource.

Archives that take in digital material quickly learn that content arrives on things: a box of floppy disks from a retiring professor, a stack of CD-Rs from a photographer, a reel of half-inch tape from a defunct lab. Before the files can be identified and preserved, the carrier itself needs a record. dcterms:medium is the DCMI Metadata Terms property for that, defined as the material or physical carrier of the resource.

Domain and range in RDFS

The property is one of the few DCMI terms with both a domain and a range, and both matter.

Declaration Class
rdfs:domain dcterms:PhysicalResource
rdfs:range dcterms:PhysicalMedium

In RDFS a domain is not a constraint that rejects bad data; it is a rule that licenses an inference. Any subject of a dcterms:medium statement can be concluded to be a dcterms:PhysicalResource. Applied to a painting or a disk that is exactly right. Applied to a PDF on a web server, a reasoner will conclude that the PDF is a physical object, and any query asking for physical holdings will then return it.

The range works the same way on the value side. Whatever appears as the object is inferred to be a dcterms:PhysicalMedium. A literal string can still be written, and many records do, but a URI pointing to a carrier term carries the type cleanly and can hold labels in several languages.

Carrier versus format

The property is a sub-property of dcterms:format, which itself refines dc:format. That lineage follows the original element’s definition, which covered file format, physical medium and dimensions together. DCMI Metadata Terms separated them: dcterms:MediaType and dcterms:FileFormat for encodings, dcterms:extent for size and duration, dcterms:medium for the carrier.

For a disk image workflow the separation maps neatly onto separate records:

  1. The carrier record describes the physical floppy disk, with dcterms:medium, a label transcription and a capacity in dcterms:extent.
  2. The disk image is a new digital resource with its own format, often a raw sector image or a forensic container.
  3. Each file extracted from the image gets a format statement from identification tools and a link back to the image.

Keeping medium off the file-level records avoids the RDFS inference problem and keeps each statement true of the thing it describes.

Values for physical media

There is no single DCMI list of carriers. Three sources cover most needs. The RDA carrier type vocabulary gives broad terms such as “computer disc”, “audiocassette” or “volume”. The Getty Art & Architecture Thesaurus covers materials and techniques for art and artifacts. For digital media, collections often keep local lists that distinguish what the broad lists do not: 5.25-inch from 3.5-inch floppies, DAT from DDS tape, CD-R from pressed CD.

The detail is not pedantry. Whether a disk can be read at all depends on knowing its exact type, its density and sometimes its formatting, and those facts come from the carrier record long before any file is identified. The format identification guide picks up where the carrier record ends.

Non-digital resources

For physical collections the property is the natural home for materials statements: “oil on canvas”, “albumen print”, “vellum”, “bronze”. Combined with dc:type values such as PhysicalObject or StillImage, it gives enough information to route an item to the right storage environment. Where both the material and the support matter, as with a painting on a panel, two medium statements are clearer than one compound string.

Example in RDF

@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .

<https://example.org/carriers/disk-0457>
    a dcterms:PhysicalResource ;
    dcterms:title "Floppy disk labeled 'Thesis drafts 1994'" ;
    dcterms:medium <https://example.org/carrier-types/floppy-3-5in> ;
    dcterms:extent "1.44 MB" .

<https://example.org/carrier-types/floppy-3-5in>
    a dcterms:PhysicalMedium ;
    rdfs:label "3.5-inch floppy disk" .

Questions about dcterms:medium

What does dcterms:medium describe?

It records the material or physical carrier of a resource: oil on canvas for a painting, gelatin silver print for a photograph, or a 3.5-inch floppy disk, a CD-R or a magnetic tape for digital content that arrived on physical media.

What are the domain and range of dcterms:medium?

The domain is dcterms:PhysicalResource and the range is dcterms:PhysicalMedium. In RDFS terms, any resource given a medium can be inferred to be a physical resource, and the value can be inferred to be a physical medium.

Should dcterms:medium be used for a born-digital file?

Generally no. Because of the RDFS domain, a medium statement on a file would let a reasoner infer the file is a physical resource. The format of the file belongs in dcterms:format; the medium belongs on a record for the carrier.

How does dcterms:medium relate to dcterms:format?

It is a sub-property of dcterms:format and of dc:format. When qualified records are reduced to simple Dublin Core, a medium value becomes a dc:format value, which matches the original definition of format as covering the physical medium.

Which vocabularies supply carrier terms?

Common choices include the RDA carrier type list, the Getty Art and Architecture Thesaurus for materials and techniques, and local lists for specific media such as tape formats. A URI from any of them fits the PhysicalMedium range.

More from DCMI Metadata Terms: properties

All 13 in this group