A related resource.
Recommended practice is to identify the related resource by means of a URI. If this is not possible or feasible, a string conforming to a formal identification system may be provided.
On its own, dct:relation means very little, and that is the design. It says a related resource exists and stops there. The value of the property comes from its family: DCMI Metadata Terms hangs more than a dozen specific relationships under it, so that any of them can fall back to the general statement when a system does not understand the specific one.
The subproperty family
Each of the following is declared a sub-property of dcterms:relation in DCMI Metadata Terms.
| Subproperty | Inverse | Meaning in brief |
|---|---|---|
| isPartOf | hasPart | physical or logical inclusion |
| isVersionOf | hasVersion | edition, adaptation, update |
| isFormatOf | hasFormat | same content, another format |
| references | isReferencedBy | cites or points to |
| replaces | isReplacedBy | supplants or supersedes |
| requires | isRequiredBy | needs the other to function |
| source | (none) | derived from |
| conformsTo | (none) | follows a standard |
dct:isFormatOf and dct:source are the two that format and preservation work uses most. conformsTo deserves a mention too: it links a resource to a standard it follows, such as a file conforming to a particular PDF/A part or a dataset following a schema, which makes it useful in format registries and validation reports. A validator that confirms a file against PDF/A-2b can record the result as a conformsTo statement pointing at the standard, and a later audit can query every file claiming that conformance when a validator bug is discovered.
Choosing the most specific property
A good habit is to ask the specific question first. Is the other resource a container? isPartOf. A different encoding of the same thing? isFormatOf. An earlier edition? isVersionOf. Something this resource cites? references. Only when every answer is no, or the relationship is genuinely unknown, does the general relation remain.
Specific properties pay off in queries. “All parts of this series” or “every derivative of this master” are one-line questions when the data uses the right sub-property, and impossible ones when everything was recorded as relation. They also give interfaces something to display: “Part of: Coastal surveys” reads better than “Related: Coastal surveys”.
The generic property still has honest uses. An exhibition that showed a document, a blog post about a dataset and a lecture that discussed a manuscript are related in ways no sub-property names. Using references for those would claim a citation that does not exist. The same applies to vague cataloging notes such as “see also” lists: they are relations in the loose sense, and forcing them into a specific sub-property adds precision that the original note never had.
Values and identifiers
The usage comment asks for a URI, with a formal identifier string as the fallback. In practice that means the same conventions as dc:identifier: DOIs and handles in resolver form, ISBNs as URNs, local records under a stable domain. A free-text pointer to an earlier tide model helps a human reader and no machine. If the related resource has no identifier at all, it often makes sense to create a minimal record for it, give it a URI and link to that.
Direction matters for every paired property. isPartOf points from the part to the whole; hasPart from the whole to the part. A batch import that reverses them produces series that are part of their own reports, and the error is easy to miss until a hierarchy display breaks.
Flattening on export
Simple Dublin Core has a single relation element. When qualified records are exported to oai_dc, every sub-property becomes dc:relation and the type of the link disappears. Some repositories compensate by prefixing the value (“IsPartOf: https://…”) in the export, a practice that is readable but not standardized and which harvesters may or may not parse. Records that also carry the full identifier of each related resource keep at least the link itself intact through the flattening.
Example in RDF
@prefix dct: <http://purl.org/dc/terms/> .
<https://example.org/reports/coastal-survey-2024.pdf>
dct:isPartOf <https://example.org/series/coastal-surveys> ;
dct:references <https://doi.org/10.5555/tide-model.2019> ;
dct:isFormatOf <https://example.org/reports/coastal-survey-2024.docx> ;
dct:relation <https://example.org/exhibitions/shorelines-2025> .
Questions about dcterms:relation
What does dct:relation mean?
dct:relation, also written dcterms:relation, states that the described resource is related to another resource, without saying how. It is the most general linking property in DCMI Metadata Terms and the parent of more specific properties such as isPartOf, isFormatOf and source.
When should the generic relation be used?
When none of the specific sub-properties fits, or when the nature of the relationship is unknown. An exhibition that displayed a report, or a website about a collection, is related to it in ways no named sub-property captures.
Are the dcterms relation subproperties paired?
Most are. isPartOf and hasPart, isVersionOf and hasVersion, isFormatOf and hasFormat, references and isReferencedBy, replaces and isReplacedBy, requires and isRequiredBy are inverse pairs. source and conformsTo have no inverse in the vocabulary.
Should the value be a URI or text?
The usage comment recommends a URI. Where a URI is not available, a string from a formal identification system such as an ISBN or DOI is the fallback. A free-text description of the related resource gives other systems nothing to link.
What happens to subproperties in simple Dublin Core?
They all map to dc:relation. A record exported to oai_dc loses the distinction between parts, formats, versions and references, which is why the specific properties are worth using in the source record even if one export flattens them.