Definition · Plain-language
Dublin Core
Dublin Core is a widely adopted metadata standard from the Dublin Core Metadata Initiative (DCMI), defining 15 core descriptive elements for describing digital and physical resources in an interoperable way.
The step most authors miss
Doing CRediT right? Don’t stop at the statement.
A CRediT statement credits you inside one paper. The recognition CRediT was built for happens when those roles are tied to you, persistently. Sign in with your ORCID — free — and claim your CRediT contributions on casrai.org, the home of the standard. They become a verified, portable part of your identity, not a line that disappears into one PDF.
Free: claim your contributions, then export a journal-ready CRediT statement, schema.org structured data, JATS XML, CSV or BibTeX — and preview your public profile. A membership publishes that profile publicly and verifies the journals you serve.
The 15 core elements
The Dublin Core Metadata Element Set defines fifteen elements for describing a resource: Title, Creator, Subject, Description, Publisher, Contributor, Date, Type, Format, Identifier, Source, Language, Relation, Coverage and Rights. Each is optional and repeatable, and all can be applied to almost any kind of resource. This deliberate simplicity is the point: a small, generic vocabulary is easy to adopt and understand, which is why Dublin Core became one of the most widely used metadata standards across libraries, archives, repositories and the web.
Why interoperability matters
Dublin Core exists to make resources describable and discoverable across system and organisational boundaries. By agreeing a shared set of elements, different repositories and search systems can exchange and interpret each other’s metadata without bespoke mapping for every pairing. This interoperability is why Dublin Core is embedded in many protocols and frameworks for sharing metadata, and why it remains a reference point for designing simple, exchangeable descriptions of data and content.
Dublin Core in context
Dublin Core is descriptive metadata aimed at discovery, and it is often used alongside richer, domain-specific schemes rather than instead of them. The DCMI has also extended the original 15 elements with additional terms and refinements for more precise description. In an enterprise data-governance setting, Dublin Core illustrates the broader principle that managed metadata depends on shared, standard vocabularies — the same principle that underlies data dictionaries, catalogues and metadata registries.
Key facts
At a glance
- Definition: a core descriptive metadata standard from DCMI
- Core set: 15 elements (Title, Creator, Subject, Date, etc.)
- Maintained by: the Dublin Core Metadata Initiative (DCMI)
- Each element: optional and repeatable
- Primary aim: interoperability and resource discovery
- Widely used in: libraries, archives, repositories and the web
Common misconceptions
What people often get wrong
Often heard: Dublin Core is a piece of software or a database product.
Actually: It is a metadata standard — an agreed vocabulary of 15 core elements — not a product. Many tools support it, but Dublin Core itself is the specification maintained by DCMI.
Often heard: Dublin Core can fully describe any resource on its own.
Actually: Its strength is simple, generic description for discovery. Rich, domain-specific needs are usually met by pairing Dublin Core with more detailed schemes rather than relying on the 15 core elements alone.
Often heard: All 15 Dublin Core elements are mandatory for every resource.
Actually: Every element is optional and repeatable. You use the elements that apply to a given resource; none is required, which is part of what makes the standard easy to adopt.
Going deeper
