Information and documentation -- The Dublin Core metadata element set -- Part 2: DCMI Properties and classes

This document establishes a vocabulary for cross-domain resource description, known as the Dublin Core metadata terms (hereafter DCMI Metadata Terms). It includes all of the properties and classes in the main namespace of DCMI Metadata Terms[1] (hereafter "the /terms/ namespace"), as published in the DCMI Recommendation document "DCMI Metadata Terms" of 2012 (DCMI-TERMS and Annex A). As explained in Annex B, these properties and classes can be identified by URIs for use in linked data.
NOTE The 15 terms of the original Dublin Core Metadata Element Set, as defined in the namespace https://purl.org/dc/elements/1.1/ (hereafter "the /elements/1.1/ namespace"), are also documented in the DCMI Recommendation "DCMI Metadata Terms" and in ISO 15836-1.
This document does not contain the following supporting terms from "DCMI Metadata Terms" specification:
a) terms from the /elements/1.1/ namespace (included in ISO 15836-1);
b) vocabulary encoding schemes;
c) syntax encoding schemes;
d) DCMI Type vocabulary;
e) terms related to the DCMI Abstract Model.
Both ISO 15836-1 and this document include the 15 so-called core terms, but in ISO 15836-1 they are from the /elements/1.1/ namespace, and in this document from the /terms/ namespace. In the latter, the terms have narrower semantics due to formal domain and range specifications.
This document does not limit what might be a resource.
This document does not provide specific implementation guidelines. The properties and classes are typically used in the context of an application profile, which constrains or specifies their use in accordance with local or community-based requirements and policies.
[1] Available at: https://purl.org/dc/terms/.

Information et documentation -- L'ensemble des éléments de métadonnées Dublin Core -- Partie 2: Titre manque

Informatika in dokumentacija - Nabor metapodatkovnih elementov Dublin Core - 2. del: Lastnosti in razredi DCMI

General Information

Status
Published
Public Enquiry End Date
20-Oct-2019
Publication Date
14-Jan-2021
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
08-Dec-2020
Due Date
12-Feb-2021
Completion Date
15-Jan-2021

RELATIONS

Buy Standard

Standard
SIST ISO 15836-2:2021
English language
31 pages
sale 10% off
Preview
sale 10% off
Preview

e-Library read for
1 day
Standard
ISO 15836-2:2019 - Information and documentation -- The Dublin Core metadata element set
English language
26 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (sample)

SLOVENSKI STANDARD
SIST ISO 15836-2:2021
01-februar-2021
Nadomešča:
SIST ISO 15836:2009
Informatika in dokumentacija - Nabor metapodatkovnih elementov Dublin Core - 2.
del: Lastnosti in razredi DCMI

Information and documentation -- The Dublin Core metadata element set -- Part 2: DCMI

Properties and classes

Information et documentation -- L'ensemble des éléments de métadonnées Dublin Core

-- Partie 2: Titre manque
Ta slovenski standard je istoveten z: ISO 15836-2:2019
ICS:
35.240.30 Uporabniške rešitve IT v IT applications in information,
informatiki, dokumentiranju in documentation and
založništvu publishing
SIST ISO 15836-2:2021 en

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------
SIST ISO 15836-2:2021
---------------------- Page: 2 ----------------------
SIST ISO 15836-2:2021
INTERNATIONAL ISO
STANDARD 15836-2
First edition
2019-12
Information and documentation — The
Dublin Core metadata element set —
Part 2:
DCMI Properties and classes
Reference number
ISO 15836-2:2019(E)
ISO 2019
---------------------- Page: 3 ----------------------
SIST ISO 15836-2:2021
ISO 15836-2:2019(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO 2019

All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may

be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting

on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address

below or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Fax: +41 22 749 09 47
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii © ISO 2019 – All rights reserved
---------------------- Page: 4 ----------------------
SIST ISO 15836-2:2021
ISO 15836-2:2019(E)
Contents Page

Foreword ........................................................................................................................................................................................................................................iv

Introduction ..................................................................................................................................................................................................................................v

1 Scope ................................................................................................................................................................................................................................. 1

2 Normative references ...................................................................................................................................................................................... 1

3 Terms, definitions and abbreviated terms ................................................................................................................................ 2

3.1 Terms and definitions ....................................................................................................................................................................... 2

3.2 DCMI properties ..................................................................................................................................................................................... 3

3.3 DCMI Classes ..........................................................................................................................................................................................17

3.4 Abbreviated terms ............................................................................................................................................................................21

4 Description of metadata terms ...........................................................................................................................................................21

Annex A (informative) Further information ..............................................................................................................................................22

Annex B (informative) Dublin Core metadata as linked data ..................................................................................................23

Bibliography .............................................................................................................................................................................................................................26

© ISO 2019 – All rights reserved iii
---------------------- Page: 5 ----------------------
SIST ISO 15836-2:2021
ISO 15836-2:2019(E)
Foreword

ISO (the International Organization for Standardization) is a worldwide federation of national standards

bodies (ISO member bodies). The work of preparing International Standards is normally carried out

through ISO technical committees. Each member body interested in a subject for which a technical

committee has been established has the right to be represented on that committee. International

organizations, governmental and non-governmental, in liaison with ISO, also take part in the work.

ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of

electrotechnical standardization.

The procedures used to develop this document and those intended for its further maintenance are

described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the

different types of ISO documents should be noted. This document was drafted in accordance with the

editorial rules of the ISO/IEC Directives, Part 2 (see www .iso .org/ directives).

Attention is drawn to the possibility that some of the elements of this document may be the subject of

patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of

any patent rights identified during the development of the document will be in the Introduction and/or

on the ISO list of patent declarations received (see www .iso .org/ patents).

Any trade name used in this document is information given for the convenience of users and does not

constitute an endorsement.

For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and

expressions related to conformity assessment, as well as information about ISO's adherence to the

World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT) see www .iso .org/

iso/ foreword .html.

This document was prepared by Technical Committee ISO/TC 46, Information and documentation,

Subcommittee SC 4, Technical interoperability.

This first edition of ISO 15836-2, together with ISO 15836-1, cancels and replaces ISO 15836:2009, which

has been technically revised. It also incorporates the Technical Corrigendum ISO 15836:2009/Cor 1:2009.

The main changes compared to the previous edition are as follows:
— the term “elements” has been changed to “properties”;

— properties and classes from the /terms/ namespace, which are not included in ISO 15836-1 have

been added;
— several term definitions have been updated;

— many examples and notes have been added, in order to make this document easier to use.

A list of all parts in the ISO 15836 series can be found on the ISO website.

Any feedback or questions on this document should be directed to the user’s national standards body. A

complete listing of these bodies can be found at www .iso .org/ members .html.
iv © ISO 2019 – All rights reserved
---------------------- Page: 6 ----------------------
SIST ISO 15836-2:2021
ISO 15836-2:2019(E)
Introduction

The properties and classes covered in this document are intended to be used in combination with

metadata terms from other, compatible vocabularies in the context of application profiles.

This set of properties and classes is expressed as an RDF vocabulary and may be used for Linked

Data. Each property and class is identified with a global identifier for use in RDF data. Creators of

non-RDF metadata can use the vocabulary in non-RDF contexts, such as XML, JSON, UML and relational

databases, by disregarding both the global identifier and the formal implications of the RDF-specific

aspects of term definitions. Such users can take domain, range, subproperty, and subclass relations as

usage suggestions and focus on the natural-language text of definitions, usage notes, and examples.

DCMI metadata terms are governed by the DCMI Usage Board (DCMI UB) . This document has been

created in close co-operation with the DCMI UB. The aim is to keep this document and DCMI metadata

terms as closely aligned as possible, both concerning the terms and their definitions and notes.

Additional information about the usage of Dublin Core terms is provided by a user guide available at

https:// purl .org/ metadata/ user _guide.

DCMI intends to revise the guidelines and link their contents more tightly with DCMI metadata terms.

Several changes have been made to DCMI metadata terms during the preparation of this document.

The reasons for these modifications are varied. DCMI usage guides and the Dublin Core Collection

Description Application Profile have been used as information sources (in the form of added notes) on

how to use given terms. Outdated references have been updated (for instance, the term “Language” is

now recommended to be used with BCP 47 instead of RFC 4646). Some terms and definitions have been

clarified (see, for example, “Available”). There is now additional guidance such as examples for terms

like Date which may have been difficult to use in a uniform way.

There are a few cases in which terms, definitions or notes have been changed (e.g. DateCopyrighted),

because the common practice has changed, or because such practice has been established since the

Dublin Core term was defined.

DCMI Usage Board may make changes and additions to DCMI metadata terms as a part of the on-going

maintenance of Dublin Core. Such modifications should be incorporated into future editions of this

document.
1) https:// dublincore .org/ usage/
© ISO 2019 – All rights reserved v
---------------------- Page: 7 ----------------------
SIST ISO 15836-2:2021
---------------------- Page: 8 ----------------------
SIST ISO 15836-2:2021
INTERNATIONAL STANDARD ISO 15836-2:2019(E)
Information and documentation — The Dublin Core
metadata element set —
Part 2:
DCMI Properties and classes
1 Scope

This document establishes a vocabulary for cross-domain resource description, known as the Dublin

Core metadata terms (hereafter DCMI Metadata Terms). It includes all of the properties and classes in

the main namespace of DCMI Metadata Terms (hereafter “the /terms/ namespace”), as published in

the DCMI Recommendation document “DCMI Metadata Terms” of 2012 (DCMI-TERMS and Annex A). As

explained in Annex B, these properties and classes can be identified by URIs for use in linked data.

NOTE The 15 terms of the original Dublin Core Metadata Element Set, as defined in the namespace https://

purl .org/ dc/ elements/ 1 .1/ (hereafter “the /elements/1.1/ namespace”), are also documented in the DCMI

Recommendation “DCMI Metadata Terms” and in ISO 15836-1.

This document does not contain the following supporting terms from “DCMI Metadata Terms”

specification:
a) terms from the /elements/1.1/ namespace (included in ISO 15836-1);
b) vocabulary encoding schemes;
c) syntax encoding schemes;
d) DCMI Type vocabulary;
e) terms related to the DCMI Abstract Model.

Both ISO 15836-1 and this document include the 15 so-called core terms, but in ISO 15836-1 they are

from the /elements/1.1/ namespace, and in this document from the /terms/ namespace. In the latter,

the terms have narrower semantics due to formal domain and range specifications.
This document does not limit what might be a resource.

This document does not provide specific implementation guidelines. The properties and classes

are typically used in the context of an application profile, which constrains or specifies their use in

accordance with local or community-based requirements and policies.
2 Normative references

The following documents are referred to in the text in such a way that some or all of their content

constitutes requirements for this document. For dated references, only the edition cited applies. For

undated references, the latest edition of the referenced document (including any amendments) applies.

ISO 15836-1, Information and documentation — The Dublin Core metadata element set — Part 1: Core

elements
2) Available at: https:// purl .org/ dc/ terms/ .
© ISO 2019 – All rights reserved 1
---------------------- Page: 9 ----------------------
SIST ISO 15836-2:2021
ISO 15836-2:2019(E)
3 Terms, definitions and abbreviated terms

For the purposes of this document, the terms and definitions given in ISO 15836-1 and the following apply.

ISO and IEC maintain terminological databases for use in standardization at the following addresses:

— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at https:// www .electropedia .org/
3.1 Terms and definitions
3.1.1
class
set of resources

Note 1 to entry: The members of a class are known as instances of the class. Classes are themselves resources.

They are often identified by URIs and may be described using RDF properties. The rdf: type property may be used

to state that a resource is an instance of a class.
[SOURCE: RDF Schema. Version 1.1]
3.1.2
domain
class of which a resource (3.1.10) described by the term is an instance

[SOURCE: DCMI Terms, https:// www .dublincore .org/ specifications/ dublin -core/ dcmi -terms/ ]

3.1.3
domain includes
suggested class for subjects of this property (3.1.6)
3.1.4
entity

something that exists apart from other things, having its own independent existence

3.1.5
literal

string of Unicode characters, such as letters or integers, optionally combined with a language tag or

datatype
3.1.6
non-literal value
either a blank node or URI (3.1.13)
3.1.7
property
relation between a subject resource and an object resource
Note 1 to entry: This is a synonym of “element”.
[SOURCE: RDF Schema. Version 1.1]
3.1.8
range
class of which a value described by the term is an instance

[SOURCE: DCMI Terms, https:// www .dublincore .org/ specifications/ dublin -core/ dcmi -terms/ ]

3.1.9
range includes
suggested class for values of this property (3.1.7)
2 © ISO 2019 – All rights reserved
---------------------- Page: 10 ----------------------
SIST ISO 15836-2:2021
ISO 15836-2:2019(E)
3.1.10
resource
entity that might be identified

Note 1 to entry: This specification does not limit the scope of what might be a resource. Anything, either abstract

or physical, can be a resource.
Note 2 to entry: In RDF, a resource may be identified by a URI (3.1.13).
[SOURCE: RFC 3986 modified.— The word“thing” has been replaced with “entity”]
3.1.11
subclass

class that is related, typically using the rdfs: subClassOf property, to another class of broader scope

(superclass), such that all instances of the subclass are instances of the superclass

[SOURCE: RDF Schema. Version 1.1]
3.1.12
subproperty

property (3.1.7) that is related, typically using the rdfs: subPropertyOf property, to another property of

broader scope (superproperty), such that all resources related by the subproperty are also related by

the superproperty
[SOURCE: RDF Schema. Version 1.1]
3.1.13
Uniform Resource Identifier
URI
identifier consisting of a sequence of characters matching the URI syntax rule

Note 1 to entry: How the identification is accomplished, assigned, or enabled, is delegated to URI scheme

specifications such as URN (3.1.14).
[SOURCE: RFC 3986]
3.1.14
Uniform Resource Name
URN

Uniform Resource Identifier (URI) (3.1.13) that is assigned under the “urn” URI scheme and a particular

URN namespace, with the intent that the URN will be a persistent, location-independent resource

identifier
[SOURCE: RFC 8141]
3.2 DCMI properties
3.2.1
abstract
summary of the resource
Label Abstract
URI https:// purl .org/ dc/ terms/ abstract
Subproperty of https:// purl .org/ dc/ terms/ description
3.2.2
accessRights

information about who may access the resource or an indication of its security status

© ISO 2019 – All rights reserved 3
---------------------- Page: 11 ----------------------
SIST ISO 15836-2:2021
ISO 15836-2:2019(E)
Label Access Rights
URI https:// purl .org/ dc/ terms/ accessRights
Subproperty of https:// purl .org/ dc/ terms/ rights
Range includes https:// purl .org/ dc/ terms/ RightsStatement

Note 1 to entry: Access rights may include information regarding access or restrictions based on privacy,

security, or other policies.
3.2.3
accrualMethod
method by which items are added to a collection
Label Accrual Method
URI https:// purl .org/ dc/ terms/ accrualMethod
Domain https:// purl .org/ dc/ dcmitype/ Collection
Range includes https:// purl .org/ dc/ terms/ MethodOfAccrual

Note 1 to entry: The recommended practice is to use a value from the Collection Description Accrual Method

vocabulary .
3.2.4
accrualPeriodicity
frequency with which items are added to a collection
Label Accrual Periodicity
URI https:// purl .org/ dc/ terms/ accrualPeriodicity
Domain https:// purl .org/ dc/ dcmitype/ Collection
Range includes https:// purl .org/ dc/ terms/ Frequency

Note 1 to entry: The recommended practice is to use a value from the Collection Description Frequency

Vocabulary .
3.2.5
accrualPolicy
policy governing the addition of items to a collection
Label Accrual Policy
URI https:// purl .org/ dc/ terms/ accrualPolicy
Domain https:// purl .org/ dc/ dcmitype/ Collection
Range includes https:// purl .org/ dc/ terms/ Policy

Note 1 to entry: The recommended practice is to use a value from the Collection Description Accrual Policy

Vocabulary .

3) https:// www .dublincore .org/ specifications/ dublin -core/ collection -description/ accrual -method/

4) https:// dublincore .org/ groups/ collections/ frequency/
5) https:// dublincore .org/ groups/ collections/ accrual -policy/
4 © ISO 2019 – All rights reserved
---------------------- Page: 12 ----------------------
SIST ISO 15836-2:2021
ISO 15836-2:2019(E)
3.2.6
alternative
alternative name for the resource
Label Alternative Title
URI https:// purl .org/ dc/ terms/ alternative
Subproperty of https:// https:// purl .org/ dc/ terms/ title
Range includes https:// https:// www .w3 .org/ 2000/ 01/ rdf -schema #Literal

Note 1 to entry: The distinction between titles and alternative titles is application-specific.

3.2.7
audience
class of agents for whom the resource (3.1.10) is intended or useful
Label Audience
URI https:// https:// purl .org/ dc/ terms/ audience
Range includes https:// purl .org/ dc/ terms/ AgentClass

Note 1 to entry: Best practice is to use this property with non-literal values from a vocabulary of audience types.

3.2.8
available
date that the resource became or will become available
Label Date Available
URI https:// purl .org/ dc/ terms/ available
Subproperty of https:// purl .org/ dc/ terms/ date
Range https:// www .w3 .org/ 2000/ 01/ rdf -schema #Literal

Note 1 to entry: The recommended practice is to describe the date, date/time, or period of time as recommended

for the property date (3.2.15), of which this is a subproperty (3.1.12).
3.2.9
bibliographicCitation
bibliographic reference for the resource
Label Bibliographic Citation
URI https:// purl .org/ dc/ terms/ bibliographicCitation
Subproperty of https:// purl .org/ dc/ terms/ identifier
Domain https:// purl .org/ dc/ terms/ BibliographicResource
Range https:// www .w3 .org/ 2000/ 01/ rdf -schema #Literal

Note 1 to entry: The recommended practice is to include sufficient bibliographic detail to identify the resource as

unambiguously as possible.
3.2.10
conformsTo
established standard to which the described resource conforms
© ISO 2019 – All rights reserved 5
---------------------- Page: 13 ----------------------
SIST ISO 15836-2:2021
ISO 15836-2:2019(E)
Label Conforms To
URI https:// purl .org/ dc/ terms/ conformsTo
Subproperty of https:// purl .org/ dc/ terms/ relation
Range includes https:// purl .org/ dc/ terms/ Standard
3.2.11
contributor
entity responsible for making contributions to the resource
Label Contributor
URI https:// purl .org/ dc/ terms/ contributor
Range includes https:// purl .org/ dc/ terms/ Agent
EXAMPLE 1 Shakespeare, William (a person)
EXAMPLE 2 https:// isni .org/ isni/ 0000000121032683 (URI for a person)
EXAMPLE 3 Hubble Space Telescope (scientific instrument)
EXAMPLE 4 UNESCO (an organization)

Note 1 to entry: The guidelines for using names of persons or organizations as creators apply to contributors.

3.2.12
coverage

spatial or temporal topic of the resource, spatial applicability of the resource, or jurisdiction under

which the resource is relevant
Label Coverage
URI https:// purl .org/ dc/ terms/ coverage
Range includes https:// purl .org/ dc/ terms/ Location
Range includes https:// purl .org/ dc/ terms/ Period
Range includes https:// purl .org/ dc/ terms/ Jurisdiction
EXAMPLE 1 1700/1799
EXAMPLE 2 Boston, MA

Note 1 to entry: Spatial topic and spatial applicability may be a named place or a location specified by its

geographic coordinates. Temporal topic may be a named period, date or date range. A jurisdiction may be a named

administrative entity or a geographic place to which the resource applies. The recommended practice is to use

a controlled vocabulary such as the Getty Thesaurus of Geographic Names (TGN). Where appropriate, named

places or time periods may be used in preference to numeric identifiers such as sets of coordinates or date ranges.

Note 2 to entry: Because coverage is so broadly defined, it is preferable to use the more specific subproperties

temporal (3.2.52) coverage and spatial (3.2.49) coverage.
3.2.13
created
date of creation of the resource
6 © ISO 2019 – All rights reserved
---------------------- Page: 14 ----------------------
SIST ISO 15836-2:2021
ISO 15836-2:2019(E)
Label Date Created
URI https:// purl .org/ dc/ terms/ created
Subproperty of https:// purl .org/ dc/ terms/ date
Range https:// www .w3 .org/ 2000/ 01/ rdf -schema #Literal

Note 1 to entry: The recommended practice is to describe the date, date/time, or period of time as recommended

for the property date (3.2.15), of which this is a subproperty (3.1.12).
3.2.14
creator
entity responsible for making the resource
Label Creator
URI https:// purl .org/ dc/ terms/ creator
Subproperty of https:// purl .org/ dc/ terms/ contributor
Range includes https:// purl .org/ dc/ terms/ Agent
EXAMPLE 1 Shakespeare, William (a person)
EXAMPLE 2 https:// isni .org/ isni/ 0000000121032683 (URI for a person)
EXAMPLE 3 UNESCO (an organization)

Note 1 to entry: The recommended practice is to identify the creator with a URI. If this is not possible or feasible,

a literal value that identifies the creator may be provided.
3.2.15
date

point or period of time associated with an event in the lifecycle of the resource

Label Date
URI https:// purl .org/ dc/ terms/ date
Range https:// www .w3 .org/ 2000/ 01/ rdf -schema #Literal
EXAMPLE 1 2018
EXAMPLE 2 2016-03-04
EXAMPLE 3 2017-11-05T08:15:30-05:00
EXAMPLE 4 1968/2015
EXAMPLE 5 2006/

Note 1 to entry: Date may be used to express temporal information at any level of granularity.

[1]

The recommended practice is to express the date, date/time or period of time according to ISO 8601-1 or a

[9]

published profile of the ISO standard, such as the W3C Note on Date and Time Formats .

Note 2 to entry: If the full date is unknown, month and year (YYYY-MM) or just year (YYYY) may be used.

Note 3 to entry: Date ranges may be specified using ISO 8601 period of time specification in which start and end

dates are separated by a “/” (slash) character. Either the start or end date may be missing.

© ISO 2019 – All rights reserved 7
---------------------- Page: 15 ----------------------
SIST ISO 15836-2:2021
ISO 15836-2:2019(E)
3.2.16
dateAccepted
date of acceptance of the resource
Label Date Accepted
URI https:// purl .org/ dc/ terms/ dateAccepted
Subproperty of https:// purl .org/ dc/ terms/ date
Range https:// www .w3 .org/ 2000/ 01/ rdf -schema #Literal

Note 1 to entry: The recommended practice is to describe the date, date/time, or period of time as recommended

for the property date (3.2.15), of which this is a subproperty (3.1.12).

Note 2 to entry: Examples of resource to which a date of acceptance may be relevant are a thesis (accepted by a

university department) or an article (accepted by a journal).
3.2.17
dateCopyrighted
date of copyright of the resource
Label Date Copyrighted
URI https:// purl .org/ dc/ terms/ dateCopyrighted
Subproperty of https:// purl .org/ dc/ terms/ date
Range https:// www .w3 .org/ 2000/ 01/ rdf -schema #Literal
Note 1 to entry: Typically a year.

Note 2 to entry: The recommended practice is to describe the date, date/time, or period of time as recommended

for the property date (3.2.15), of which this is a subproperty (3.1.12).
3.2.18
dateSubmitted
date of submission of the resource
Label Date Submitted
URI https:// purl .org/ dc/ terms/ dateSubmitted
Subproperty of https:// purl .org/ dc/ terms/ date
Range https:// www .w3 .org/ 2000/ 01/ rdf -schema #Literal

Note 1 to entry: The recommended practice is to describe the date, date/time, or period of time as recommended

for the property date (3.2.15), of which this is a subproperty (3.1.12).

Note 2 to entry: Examples of resources to which a “date submitted” may be relevant include a thesis (submitted

to a university department) or an article (submitted to a journal).
3.2.19
description
account of the resource
Label Description
URI https:// purl .org/ dc/ terms/ description
8 © ISO 2019 – All rights reserved
---------------------- Page: 16 ----------------------
SIST ISO 15836-2:2021
ISO 15836-2:2019(E)

Note 1 to entry: Description may include but is not limited to: an abstract, a table of contents, a graphical

representation, or a free-text account of the resource.
3.2.20
educationLevel

class of agents, defined in terms of progression through an educational or training context, for which

the described resource is intended
Label Audience Education Level
URI https:// purl .org/ dc/ terms/ educationLevel
Subproperty of https:// purl .org/ dc/ terms/ audience
Range includes https:// purl .org/ dc/ terms/ AgentClass
3.2.21
extent
size or duration of the resource
Label Extent
URI https:// purl .org/ dc/ terms/ extent
Subproperty of https:// purl .org/ dc/ terms/ format
Range includes https:// purl .org/ dc/ terms/ SizeOrDuration
EXAMPLE 1 PT2H7M30S (2 h, 7 min and 30 s according to ISO 8601-1).
EXAMPLE 2 5,6 MB (file size in megabytes).

Note 1 to entry: The recommended practice is to specify the file size in megabytes and duration in ISO 8601 format.

3.2.22
format
file format, physical medium, or dimensions of the resource
Label Format
URI https:// purl .org/ dc/ terms/ format
Range includes https:// purl .org/ dc/ terms/ MediaType
Range includes https:// purl .org/ dc/ terms/ Extent
EXAMPLE 1 text/xml.
EXAMPLE 2 https:// id .loc .gov/ vocabulary/ mvidformat/ dvd.
EXAMPLE 3 23 cm.

Note 1 to entry: The recommended practice is to use a controlled vocabulary where available. For example, for

file formats one could use the list of Internet Media Types [MIME].
Note 2 to entry: Examples of dimensions include size and duration.
3.2.23
hasFormat

related resource that is substantially the same as the pre-existing described resource, but in

another format
© ISO 2019 – All rights reserved 9
---------------------- Page: 17 ----------------------
SIST ISO 15836-2:2021
ISO 15836-2:2019(E)
Label Has Format
URI https:// purl .org/ dc/ terms/ hasFormat
Subproperty of https:// purl .org/ dc/ terms/ relation
Note 1 to entry: This property is intended to be used with non-literal values.
Note 2 to entry: This property is an inverse property of isFormatOf (3.2.28).
3.2.24
hasPart

related resource that is included either physically or logically in the described resource

Label Has Part
URI https:// purl .org/ dc/ terms/ hasPart
Subproperty of https:// purl .org/ dc/ terms/ relation
Note 1 to entry: This property is intended to be used with non-literal values.
Note 2 to entry: This property is an inverse property of isPartOf (3.2.29).
3.2.25
hasVersion

related resource that is a version, edition, or adaptation of the described resource

Label Has Version
URI https:// purl .org/ dc/ terms/ hasVersion
Subproperty of https:// purl .org/ dc/ terms/ relation

Note 1 to entry: Changes in version imply substantive changes in content rather than differences in format.

Note 2 to entry: This property is intended to be used with non-literal values.
Note 3 to entry: This property is an inverse property of isVersionOf (3.2.34).
3.2.26
identifier
unambiguous reference to the resource within a given context
Label Identifier
URI https:// purl .org/ dc/ terms/ identifier
Range https:// www .w3 .org/ 2000/ 01/ rdf -schema #Literal
EXAMPLE 1 978-3-16-148410-0
EXAMPLE 2 https:// doi .org/ 10 .17863/ CAM .11283
EXAMPLE 3 URN: NBN: fi -fd2017 -00011868

Note 1 to entry: The recommended practice is to identify the resource by means of a string conforming to an

identification system. Examples above represent International Standard Book Number (ISBN), Digital Object

Identifier (DOI) and Uniform Resource Name (URN).
Note 2 to entry: Persistent identifiers should be provided as HTTP URIs.
10 © ISO 2019 – All rights reserved
---------------------- Page: 18 ----------------------
SIST ISO 15836-2:2021
ISO 15836-2:2019(E)
3.2.27
...

INTERNATIONAL ISO
STANDARD 15836-2
First edition
2019-12
Information and documentation — The
Dublin Core metadata element set —
Part 2:
DCMI Properties and classes
Reference number
ISO 15836-2:2019(E)
ISO 2019
---------------------- Page: 1 ----------------------
ISO 15836-2:2019(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO 2019

All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may

be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting

on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address

below or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Fax: +41 22 749 09 47
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii © ISO 2019 – All rights reserved
---------------------- Page: 2 ----------------------
ISO 15836-2:2019(E)
Contents Page

Foreword ........................................................................................................................................................................................................................................iv

Introduction ..................................................................................................................................................................................................................................v

1 Scope ................................................................................................................................................................................................................................. 1

2 Normative references ...................................................................................................................................................................................... 1

3 Terms, definitions and abbreviated terms ................................................................................................................................ 2

3.1 Terms and definitions ....................................................................................................................................................................... 2

3.2 DCMI properties ..................................................................................................................................................................................... 3

3.3 DCMI Classes ..........................................................................................................................................................................................17

3.4 Abbreviated terms ............................................................................................................................................................................21

4 Description of metadata terms ...........................................................................................................................................................21

Annex A (informative) Further information ..............................................................................................................................................22

Annex B (informative) Dublin Core metadata as linked data ..................................................................................................23

Bibliography .............................................................................................................................................................................................................................26

© ISO 2019 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO 15836-2:2019(E)
Foreword

ISO (the International Organization for Standardization) is a worldwide federation of national standards

bodies (ISO member bodies). The work of preparing International Standards is normally carried out

through ISO technical committees. Each member body interested in a subject for which a technical

committee has been established has the right to be represented on that committee. International

organizations, governmental and non-governmental, in liaison with ISO, also take part in the work.

ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of

electrotechnical standardization.

The procedures used to develop this document and those intended for its further maintenance are

described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the

different types of ISO documents should be noted. This document was drafted in accordance with the

editorial rules of the ISO/IEC Directives, Part 2 (see www .iso .org/ directives).

Attention is drawn to the possibility that some of the elements of this document may be the subject of

patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of

any patent rights identified during the development of the document will be in the Introduction and/or

on the ISO list of patent declarations received (see www .iso .org/ patents).

Any trade name used in this document is information given for the convenience of users and does not

constitute an endorsement.

For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and

expressions related to conformity assessment, as well as information about ISO's adherence to the

World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT) see www .iso .org/

iso/ foreword .html.

This document was prepared by Technical Committee ISO/TC 46, Information and documentation,

Subcommittee SC 4, Technical interoperability.

This first edition of ISO 15836-2, together with ISO 15836-1, cancels and replaces ISO 15836:2009, which

has been technically revised. It also incorporates the Technical Corrigendum ISO 15836:2009/Cor 1:2009.

The main changes compared to the previous edition are as follows:
— the term “elements” has been changed to “properties”;

— properties and classes from the /terms/ namespace, which are not included in ISO 15836-1 have

been added;
— several term definitions have been updated;

— many examples and notes have been added, in order to make this document easier to use.

A list of all parts in the ISO 15836 series can be found on the ISO website.

Any feedback or questions on this document should be directed to the user’s national standards body. A

complete listing of these bodies can be found at www .iso .org/ members .html.
iv © ISO 2019 – All rights reserved
---------------------- Page: 4 ----------------------
ISO 15836-2:2019(E)
Introduction

The properties and classes covered in this document are intended to be used in combination with

metadata terms from other, compatible vocabularies in the context of application profiles.

This set of properties and classes is expressed as an RDF vocabulary and may be used for Linked

Data. Each property and class is identified with a global identifier for use in RDF data. Creators of

non-RDF metadata can use the vocabulary in non-RDF contexts, such as XML, JSON, UML and relational

databases, by disregarding both the global identifier and the formal implications of the RDF-specific

aspects of term definitions. Such users can take domain, range, subproperty, and subclass relations as

usage suggestions and focus on the natural-language text of definitions, usage notes, and examples.

DCMI metadata terms are governed by the DCMI Usage Board (DCMI UB) . This document has been

created in close co-operation with the DCMI UB. The aim is to keep this document and DCMI metadata

terms as closely aligned as possible, both concerning the terms and their definitions and notes.

Additional information about the usage of Dublin Core terms is provided by a user guide available at

https:// purl .org/ metadata/ user _guide.

DCMI intends to revise the guidelines and link their contents more tightly with DCMI metadata terms.

Several changes have been made to DCMI metadata terms during the preparation of this document.

The reasons for these modifications are varied. DCMI usage guides and the Dublin Core Collection

Description Application Profile have been used as information sources (in the form of added notes) on

how to use given terms. Outdated references have been updated (for instance, the term “Language” is

now recommended to be used with BCP 47 instead of RFC 4646). Some terms and definitions have been

clarified (see, for example, “Available”). There is now additional guidance such as examples for terms

like Date which may have been difficult to use in a uniform way.

There are a few cases in which terms, definitions or notes have been changed (e.g. DateCopyrighted),

because the common practice has changed, or because such practice has been established since the

Dublin Core term was defined.

DCMI Usage Board may make changes and additions to DCMI metadata terms as a part of the on-going

maintenance of Dublin Core. Such modifications should be incorporated into future editions of this

document.
1) https:// dublincore .org/ usage/
© ISO 2019 – All rights reserved v
---------------------- Page: 5 ----------------------
INTERNATIONAL STANDARD ISO 15836-2:2019(E)
Information and documentation — The Dublin Core
metadata element set —
Part 2:
DCMI Properties and classes
1 Scope

This document establishes a vocabulary for cross-domain resource description, known as the Dublin

Core metadata terms (hereafter DCMI Metadata Terms). It includes all of the properties and classes in

the main namespace of DCMI Metadata Terms (hereafter “the /terms/ namespace”), as published in

the DCMI Recommendation document “DCMI Metadata Terms” of 2012 (DCMI-TERMS and Annex A). As

explained in Annex B, these properties and classes can be identified by URIs for use in linked data.

NOTE The 15 terms of the original Dublin Core Metadata Element Set, as defined in the namespace https://

purl .org/ dc/ elements/ 1 .1/ (hereafter “the /elements/1.1/ namespace”), are also documented in the DCMI

Recommendation “DCMI Metadata Terms” and in ISO 15836-1.

This document does not contain the following supporting terms from “DCMI Metadata Terms”

specification:
a) terms from the /elements/1.1/ namespace (included in ISO 15836-1);
b) vocabulary encoding schemes;
c) syntax encoding schemes;
d) DCMI Type vocabulary;
e) terms related to the DCMI Abstract Model.

Both ISO 15836-1 and this document include the 15 so-called core terms, but in ISO 15836-1 they are

from the /elements/1.1/ namespace, and in this document from the /terms/ namespace. In the latter,

the terms have narrower semantics due to formal domain and range specifications.
This document does not limit what might be a resource.

This document does not provide specific implementation guidelines. The properties and classes

are typically used in the context of an application profile, which constrains or specifies their use in

accordance with local or community-based requirements and policies.
2 Normative references

The following documents are referred to in the text in such a way that some or all of their content

constitutes requirements for this document. For dated references, only the edition cited applies. For

undated references, the latest edition of the referenced document (including any amendments) applies.

ISO 15836-1, Information and documentation — The Dublin Core metadata element set — Part 1: Core

elements
2) Available at: https:// purl .org/ dc/ terms/ .
© ISO 2019 – All rights reserved 1
---------------------- Page: 6 ----------------------
ISO 15836-2:2019(E)
3 Terms, definitions and abbreviated terms

For the purposes of this document, the terms and definitions given in ISO 15836-1 and the following apply.

ISO and IEC maintain terminological databases for use in standardization at the following addresses:

— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at https:// www .electropedia .org/
3.1 Terms and definitions
3.1.1
class
set of resources

Note 1 to entry: The members of a class are known as instances of the class. Classes are themselves resources.

They are often identified by URIs and may be described using RDF properties. The rdf: type property may be used

to state that a resource is an instance of a class.
[SOURCE: RDF Schema. Version 1.1]
3.1.2
domain
class of which a resource (3.1.10) described by the term is an instance

[SOURCE: DCMI Terms, https:// www .dublincore .org/ specifications/ dublin -core/ dcmi -terms/ ]

3.1.3
domain includes
suggested class for subjects of this property (3.1.6)
3.1.4
entity

something that exists apart from other things, having its own independent existence

3.1.5
literal

string of Unicode characters, such as letters or integers, optionally combined with a language tag or

datatype
3.1.6
non-literal value
either a blank node or URI (3.1.13)
3.1.7
property
relation between a subject resource and an object resource
Note 1 to entry: This is a synonym of “element”.
[SOURCE: RDF Schema. Version 1.1]
3.1.8
range
class of which a value described by the term is an instance

[SOURCE: DCMI Terms, https:// www .dublincore .org/ specifications/ dublin -core/ dcmi -terms/ ]

3.1.9
range includes
suggested class for values of this property (3.1.7)
2 © ISO 2019 – All rights reserved
---------------------- Page: 7 ----------------------
ISO 15836-2:2019(E)
3.1.10
resource
entity that might be identified

Note 1 to entry: This specification does not limit the scope of what might be a resource. Anything, either abstract

or physical, can be a resource.
Note 2 to entry: In RDF, a resource may be identified by a URI (3.1.13).
[SOURCE: RFC 3986 modified.— The word“thing” has been replaced with “entity”]
3.1.11
subclass

class that is related, typically using the rdfs: subClassOf property, to another class of broader scope

(superclass), such that all instances of the subclass are instances of the superclass

[SOURCE: RDF Schema. Version 1.1]
3.1.12
subproperty

property (3.1.7) that is related, typically using the rdfs: subPropertyOf property, to another property of

broader scope (superproperty), such that all resources related by the subproperty are also related by

the superproperty
[SOURCE: RDF Schema. Version 1.1]
3.1.13
Uniform Resource Identifier
URI
identifier consisting of a sequence of characters matching the URI syntax rule

Note 1 to entry: How the identification is accomplished, assigned, or enabled, is delegated to URI scheme

specifications such as URN (3.1.14).
[SOURCE: RFC 3986]
3.1.14
Uniform Resource Name
URN

Uniform Resource Identifier (URI) (3.1.13) that is assigned under the “urn” URI scheme and a particular

URN namespace, with the intent that the URN will be a persistent, location-independent resource

identifier
[SOURCE: RFC 8141]
3.2 DCMI properties
3.2.1
abstract
summary of the resource
Label Abstract
URI https:// purl .org/ dc/ terms/ abstract
Subproperty of https:// purl .org/ dc/ terms/ description
3.2.2
accessRights

information about who may access the resource or an indication of its security status

© ISO 2019 – All rights reserved 3
---------------------- Page: 8 ----------------------
ISO 15836-2:2019(E)
Label Access Rights
URI https:// purl .org/ dc/ terms/ accessRights
Subproperty of https:// purl .org/ dc/ terms/ rights
Range includes https:// purl .org/ dc/ terms/ RightsStatement

Note 1 to entry: Access rights may include information regarding access or restrictions based on privacy,

security, or other policies.
3.2.3
accrualMethod
method by which items are added to a collection
Label Accrual Method
URI https:// purl .org/ dc/ terms/ accrualMethod
Domain https:// purl .org/ dc/ dcmitype/ Collection
Range includes https:// purl .org/ dc/ terms/ MethodOfAccrual

Note 1 to entry: The recommended practice is to use a value from the Collection Description Accrual Method

vocabulary .
3.2.4
accrualPeriodicity
frequency with which items are added to a collection
Label Accrual Periodicity
URI https:// purl .org/ dc/ terms/ accrualPeriodicity
Domain https:// purl .org/ dc/ dcmitype/ Collection
Range includes https:// purl .org/ dc/ terms/ Frequency

Note 1 to entry: The recommended practice is to use a value from the Collection Description Frequency

Vocabulary .
3.2.5
accrualPolicy
policy governing the addition of items to a collection
Label Accrual Policy
URI https:// purl .org/ dc/ terms/ accrualPolicy
Domain https:// purl .org/ dc/ dcmitype/ Collection
Range includes https:// purl .org/ dc/ terms/ Policy

Note 1 to entry: The recommended practice is to use a value from the Collection Description Accrual Policy

Vocabulary .

3) https:// www .dublincore .org/ specifications/ dublin -core/ collection -description/ accrual -method/

4) https:// dublincore .org/ groups/ collections/ frequency/
5) https:// dublincore .org/ groups/ collections/ accrual -policy/
4 © ISO 2019 – All rights reserved
---------------------- Page: 9 ----------------------
ISO 15836-2:2019(E)
3.2.6
alternative
alternative name for the resource
Label Alternative Title
URI https:// purl .org/ dc/ terms/ alternative
Subproperty of https:// https:// purl .org/ dc/ terms/ title
Range includes https:// https:// www .w3 .org/ 2000/ 01/ rdf -schema #Literal

Note 1 to entry: The distinction between titles and alternative titles is application-specific.

3.2.7
audience
class of agents for whom the resource (3.1.10) is intended or useful
Label Audience
URI https:// https:// purl .org/ dc/ terms/ audience
Range includes https:// purl .org/ dc/ terms/ AgentClass

Note 1 to entry: Best practice is to use this property with non-literal values from a vocabulary of audience types.

3.2.8
available
date that the resource became or will become available
Label Date Available
URI https:// purl .org/ dc/ terms/ available
Subproperty of https:// purl .org/ dc/ terms/ date
Range https:// www .w3 .org/ 2000/ 01/ rdf -schema #Literal

Note 1 to entry: The recommended practice is to describe the date, date/time, or period of time as recommended

for the property date (3.2.15), of which this is a subproperty (3.1.12).
3.2.9
bibliographicCitation
bibliographic reference for the resource
Label Bibliographic Citation
URI https:// purl .org/ dc/ terms/ bibliographicCitation
Subproperty of https:// purl .org/ dc/ terms/ identifier
Domain https:// purl .org/ dc/ terms/ BibliographicResource
Range https:// www .w3 .org/ 2000/ 01/ rdf -schema #Literal

Note 1 to entry: The recommended practice is to include sufficient bibliographic detail to identify the resource as

unambiguously as possible.
3.2.10
conformsTo
established standard to which the described resource conforms
© ISO 2019 – All rights reserved 5
---------------------- Page: 10 ----------------------
ISO 15836-2:2019(E)
Label Conforms To
URI https:// purl .org/ dc/ terms/ conformsTo
Subproperty of https:// purl .org/ dc/ terms/ relation
Range includes https:// purl .org/ dc/ terms/ Standard
3.2.11
contributor
entity responsible for making contributions to the resource
Label Contributor
URI https:// purl .org/ dc/ terms/ contributor
Range includes https:// purl .org/ dc/ terms/ Agent
EXAMPLE 1 Shakespeare, William (a person)
EXAMPLE 2 https:// isni .org/ isni/ 0000000121032683 (URI for a person)
EXAMPLE 3 Hubble Space Telescope (scientific instrument)
EXAMPLE 4 UNESCO (an organization)

Note 1 to entry: The guidelines for using names of persons or organizations as creators apply to contributors.

3.2.12
coverage

spatial or temporal topic of the resource, spatial applicability of the resource, or jurisdiction under

which the resource is relevant
Label Coverage
URI https:// purl .org/ dc/ terms/ coverage
Range includes https:// purl .org/ dc/ terms/ Location
Range includes https:// purl .org/ dc/ terms/ Period
Range includes https:// purl .org/ dc/ terms/ Jurisdiction
EXAMPLE 1 1700/1799
EXAMPLE 2 Boston, MA

Note 1 to entry: Spatial topic and spatial applicability may be a named place or a location specified by its

geographic coordinates. Temporal topic may be a named period, date or date range. A jurisdiction may be a named

administrative entity or a geographic place to which the resource applies. The recommended practice is to use

a controlled vocabulary such as the Getty Thesaurus of Geographic Names (TGN). Where appropriate, named

places or time periods may be used in preference to numeric identifiers such as sets of coordinates or date ranges.

Note 2 to entry: Because coverage is so broadly defined, it is preferable to use the more specific subproperties

temporal (3.2.52) coverage and spatial (3.2.49) coverage.
3.2.13
created
date of creation of the resource
6 © ISO 2019 – All rights reserved
---------------------- Page: 11 ----------------------
ISO 15836-2:2019(E)
Label Date Created
URI https:// purl .org/ dc/ terms/ created
Subproperty of https:// purl .org/ dc/ terms/ date
Range https:// www .w3 .org/ 2000/ 01/ rdf -schema #Literal

Note 1 to entry: The recommended practice is to describe the date, date/time, or period of time as recommended

for the property date (3.2.15), of which this is a subproperty (3.1.12).
3.2.14
creator
entity responsible for making the resource
Label Creator
URI https:// purl .org/ dc/ terms/ creator
Subproperty of https:// purl .org/ dc/ terms/ contributor
Range includes https:// purl .org/ dc/ terms/ Agent
EXAMPLE 1 Shakespeare, William (a person)
EXAMPLE 2 https:// isni .org/ isni/ 0000000121032683 (URI for a person)
EXAMPLE 3 UNESCO (an organization)

Note 1 to entry: The recommended practice is to identify the creator with a URI. If this is not possible or feasible,

a literal value that identifies the creator may be provided.
3.2.15
date

point or period of time associated with an event in the lifecycle of the resource

Label Date
URI https:// purl .org/ dc/ terms/ date
Range https:// www .w3 .org/ 2000/ 01/ rdf -schema #Literal
EXAMPLE 1 2018
EXAMPLE 2 2016-03-04
EXAMPLE 3 2017-11-05T08:15:30-05:00
EXAMPLE 4 1968/2015
EXAMPLE 5 2006/

Note 1 to entry: Date may be used to express temporal information at any level of granularity.

[1]

The recommended practice is to express the date, date/time or period of time according to ISO 8601-1 or a

[9]

published profile of the ISO standard, such as the W3C Note on Date and Time Formats .

Note 2 to entry: If the full date is unknown, month and year (YYYY-MM) or just year (YYYY) may be used.

Note 3 to entry: Date ranges may be specified using ISO 8601 period of time specification in which start and end

dates are separated by a “/” (slash) character. Either the start or end date may be missing.

© ISO 2019 – All rights reserved 7
---------------------- Page: 12 ----------------------
ISO 15836-2:2019(E)
3.2.16
dateAccepted
date of acceptance of the resource
Label Date Accepted
URI https:// purl .org/ dc/ terms/ dateAccepted
Subproperty of https:// purl .org/ dc/ terms/ date
Range https:// www .w3 .org/ 2000/ 01/ rdf -schema #Literal

Note 1 to entry: The recommended practice is to describe the date, date/time, or period of time as recommended

for the property date (3.2.15), of which this is a subproperty (3.1.12).

Note 2 to entry: Examples of resource to which a date of acceptance may be relevant are a thesis (accepted by a

university department) or an article (accepted by a journal).
3.2.17
dateCopyrighted
date of copyright of the resource
Label Date Copyrighted
URI https:// purl .org/ dc/ terms/ dateCopyrighted
Subproperty of https:// purl .org/ dc/ terms/ date
Range https:// www .w3 .org/ 2000/ 01/ rdf -schema #Literal
Note 1 to entry: Typically a year.

Note 2 to entry: The recommended practice is to describe the date, date/time, or period of time as recommended

for the property date (3.2.15), of which this is a subproperty (3.1.12).
3.2.18
dateSubmitted
date of submission of the resource
Label Date Submitted
URI https:// purl .org/ dc/ terms/ dateSubmitted
Subproperty of https:// purl .org/ dc/ terms/ date
Range https:// www .w3 .org/ 2000/ 01/ rdf -schema #Literal

Note 1 to entry: The recommended practice is to describe the date, date/time, or period of time as recommended

for the property date (3.2.15), of which this is a subproperty (3.1.12).

Note 2 to entry: Examples of resources to which a “date submitted” may be relevant include a thesis (submitted

to a university department) or an article (submitted to a journal).
3.2.19
description
account of the resource
Label Description
URI https:// purl .org/ dc/ terms/ description
8 © ISO 2019 – All rights reserved
---------------------- Page: 13 ----------------------
ISO 15836-2:2019(E)

Note 1 to entry: Description may include but is not limited to: an abstract, a table of contents, a graphical

representation, or a free-text account of the resource.
3.2.20
educationLevel

class of agents, defined in terms of progression through an educational or training context, for which

the described resource is intended
Label Audience Education Level
URI https:// purl .org/ dc/ terms/ educationLevel
Subproperty of https:// purl .org/ dc/ terms/ audience
Range includes https:// purl .org/ dc/ terms/ AgentClass
3.2.21
extent
size or duration of the resource
Label Extent
URI https:// purl .org/ dc/ terms/ extent
Subproperty of https:// purl .org/ dc/ terms/ format
Range includes https:// purl .org/ dc/ terms/ SizeOrDuration
EXAMPLE 1 PT2H7M30S (2 h, 7 min and 30 s according to ISO 8601-1).
EXAMPLE 2 5,6 MB (file size in megabytes).

Note 1 to entry: The recommended practice is to specify the file size in megabytes and duration in ISO 8601 format.

3.2.22
format
file format, physical medium, or dimensions of the resource
Label Format
URI https:// purl .org/ dc/ terms/ format
Range includes https:// purl .org/ dc/ terms/ MediaType
Range includes https:// purl .org/ dc/ terms/ Extent
EXAMPLE 1 text/xml.
EXAMPLE 2 https:// id .loc .gov/ vocabulary/ mvidformat/ dvd.
EXAMPLE 3 23 cm.

Note 1 to entry: The recommended practice is to use a controlled vocabulary where available. For example, for

file formats one could use the list of Internet Media Types [MIME].
Note 2 to entry: Examples of dimensions include size and duration.
3.2.23
hasFormat

related resource that is substantially the same as the pre-existing described resource, but in

another format
© ISO 2019 – All rights reserved 9
---------------------- Page: 14 ----------------------
ISO 15836-2:2019(E)
Label Has Format
URI https:// purl .org/ dc/ terms/ hasFormat
Subproperty of https:// purl .org/ dc/ terms/ relation
Note 1 to entry: This property is intended to be used with non-literal values.
Note 2 to entry: This property is an inverse property of isFormatOf (3.2.28).
3.2.24
hasPart

related resource that is included either physically or logically in the described resource

Label Has Part
URI https:// purl .org/ dc/ terms/ hasPart
Subproperty of https:// purl .org/ dc/ terms/ relation
Note 1 to entry: This property is intended to be used with non-literal values.
Note 2 to entry: This property is an inverse property of isPartOf (3.2.29).
3.2.25
hasVersion

related resource that is a version, edition, or adaptation of the described resource

Label Has Version
URI https:// purl .org/ dc/ terms/ hasVersion
Subproperty of https:// purl .org/ dc/ terms/ relation

Note 1 to entry: Changes in version imply substantive changes in content rather than differences in format.

Note 2 to entry: This property is intended to be used with non-literal values.
Note 3 to entry: This property is an inverse property of isVersionOf (3.2.34).
3.2.26
identifier
unambiguous reference to the resource within a given context
Label Identifier
URI https:// purl .org/ dc/ terms/ identifier
Range https:// www .w3 .org/ 2000/ 01/ rdf -schema #Literal
EXAMPLE 1 978-3-16-148410-0
EXAMPLE 2 https:// doi .org/ 10 .17863/ CAM .11283
EXAMPLE 3 URN: NBN: fi -fd2017 -00011868

Note 1 to entry: The recommended practice is to identify the resource by means of a string conforming to an

identification system. Examples above represent International Standard Book Number (ISBN), Digital Object

Identifier (DOI) and Uniform Resource Name (URN).
Note 2 to entry: Persistent identifiers should be provided as HTTP URIs.
10 © ISO 2019 – All rights reserved
---------------------- Page: 15 ----------------------
ISO 15836-2:2019(E)
3.2.27
instructionalMethod

process, used to engender knowledge, attitudes and skills, that the described resource is designed

to support
Label Instructional Method
URI https:// purl .org/ dc/ terms/ instructionalMethod
Range includes https:// purl .org/ dc/ terms/ MethodOfInstruction

Note 1 to entry: Instructional Method (3.2.27) typically includes ways of presenting instructional materials or

conducting instructional activities, patterns of learner-to-learner and learner-to-instructor interactions, and

mechanisms by which group and individual levels of learning are measured. Instructional methods include all

aspects of the instruction and learning processes from planning and implementation through evaluation and

feedback.
3.2.28
isFormatOf

pre-existing related resource that is substantially the same as the described resource, but in

another format
Label Is Format Of
URI https:// purl .org/ dc/ terms/ isFormatOf
Subproperty of https:// purl .org/ dc/ terms/ relation
Note 1 to entry: This property is intended to be used with non-literal values.
Note 2 to entry: This property is an inverse property of hasFormat (3.2.23).
3.2.29
isPartOf

related resource in which the described resource is physically or logically included

Label Is Part Of
URI https:// purl .org/ dc/ terms/ isPartOf
Subproperty of https:// purl .o
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.