Skip to content
Property · Dublin Core elements

dc.type and the DCMI Type Vocabulary, explained with examples

Published Formatory editorial team
http://purl.org/dc/elements/1.1/type

The nature or genre of the resource.

Recommended practice is to use a controlled vocabulary such as the DCMI Type Vocabulary [DCMI-TYPE]. To describe the file format, physical medium, or dimensions of the resource, use the property Format.

The type element is where a record states what a resource is: a text, an image, a dataset, a piece of software. In HTML metadata and in repository platforms it is usually written dc.type or DC.type, and in RDF it is dc:type with the namespace http://purl.org/dc/elements/1.1/. All of these are the same element, defined by DCMI as the nature or genre of the resource.

The DCMI Type Vocabulary

The definition leaves the value open, and the usage comment fills the gap with a recommendation: use a controlled vocabulary, such as the DCMI Type Vocabulary. That list is deliberately small, which is its main strength. Twelve terms are enough to sort material from libraries, archives, museums and data repositories into groups that make sense across all of them.

Term Typical resources
Collection an aggregation described as a whole, such as a fonds or a series
Dataset tables, databases, structured data in CSV or JSON
Event an exhibition, a conference, a performance
Image any visual representation other than text
InteractiveResource web applications, online forms, games
MovingImage film, video, animation
PhysicalObject a sculpture, a tool, a specimen
Service a web service or a reference desk
Software source code and executable programs
Sound music, speech, audio recordings
StillImage photographs, paintings, scanned maps
Text books, articles, letters, transcripts

The vocabulary has changed little since its early versions. Image was later joined by two narrower terms, and the broader one stayed so that existing records remained valid. StillImage and MovingImage are sub-classes of Image, so a system indexing types can roll them up. A scanned letter is the classic hard case. It arrives as an image file, but its nature is textual, and most collections type it as Text with the image format recorded in dc:format.

dc.type in HTML and repositories

The DCMI recommendation for embedding metadata in HTML pages uses link elements to declare the schemas and meta elements for the values, as in the example on this page. The scheme attribute tells a reader that “Dataset” comes from the DCMI type list and not from some local vocabulary with the same word in it.

Repository platforms such as DSpace store the element under the field name dc.type, and there it often carries local values: “Thesis”, “Article”, “Working Paper”. That is allowed (the DCMI list is recommended, not required), but it has consequences once records are harvested. An aggregator receiving “Article” from one source, “Text” from another and “journal article” from a third has to map them before any type facet works. A sensible pattern is two values: one DCMI term for interoperability and one local genre term for the home system.

The broad list also hides distinctions that users care about. Text covers a novel, a court ruling, a spreadsheet of names exported as plain text and a scanned handwritten diary. Searchers looking for maps, theses or oral histories will not find them through DCMI types alone, which is why genre vocabularies such as the Library of Congress Genre/Form Terms or the Getty Art & Architecture Thesaurus often sit beside them in the second value.

Where type ends and other elements begin

The comment says it directly: file format, physical medium and dimensions go in the Format element. Type is about the nature of the content, independent of its encoding. The same lecture can be MovingImage as a video, Sound as an audio file and Text as a transcript, and each is a separate resource with its own type.

Type is also not a subject. A dataset about photography is still a Dataset; the topic belongs in dcterms:subject. In qualified records, dcterms:type carries the same meaning with a formal range of rdfs:Class, which is why linked-data records point it at http://purl.org/dc/dcmitype/Dataset and avoid the bare word. Simple Dublin Core in an OAI-PMH feed stays with the literal term, case and spelling exactly as published, so StillImage and never “Still image”.

Example in RDF

<head>
  <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/">
  <link rel="schema.DCTERMS" href="http://purl.org/dc/terms/">
  <meta name="DC.title" content="Tide tables for the northern estuary, 2025">
  <meta name="DC.type" scheme="DCTERMS.DCMIType" content="Dataset">
  <meta name="DC.format" scheme="DCTERMS.IMT" content="text/csv">
</head>

Questions about dc:type

What is dc.type?

dc.type is the HTML meta and repository field form of the Dublin Core type element, which records the nature or genre of a resource. Values such as Text, StillImage, Sound or Dataset usually come from the DCMI Type Vocabulary.

What is the DCMI Type Vocabulary?

It is a short list of general resource types maintained by DCMI in the namespace http://purl.org/dc/dcmitype/. Its terms are Collection, Dataset, Event, Image, InteractiveResource, MovingImage, PhysicalObject, Service, Software, Sound, StillImage and Text.

Can dc:type use values outside the DCMI list?

Yes. The DCMI list is recommended, not mandatory. Many collections add a second dc:type value from a more specific genre vocabulary, such as thesis, map or field recording, while keeping one DCMI term for cross-collection searching.

Is a PDF a type or a format?

PDF is a format. The type of a PDF depends on what it contains: a report is Text, a scanned photograph is StillImage, a spreadsheet saved as PDF may still be described as Dataset. Format goes in dc:format.

Should DCMI type values be capitalized?

Yes. The vocabulary terms are written in UpperCamelCase, such as StillImage and MovingImage. Lowercase or spaced variants like still image will not match the controlled term in systems that validate against the vocabulary.

More from Dublin Core elements

All 9 in this group