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
Publication Date
04-Dec-2019
Current Stage
9020 - International Standard under periodical review
Start Date
15-Oct-2024
Completion Date
15-Oct-2024

Relations

Buy Standard

Standard
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 — Part 2: DCMI Properties and classes Released:12/5/2019
English language
26 pages
sale 15% off
Preview
sale 15% off
Preview
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
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
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

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 2019
© 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

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
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

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.
1)
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/
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
2)
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/ .
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

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.
...


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 2019
© 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

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
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

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.
1)
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/
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
2)
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/ .
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

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 particul
...


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 2019
© 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

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
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

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.
1)
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/
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
2)
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/ .
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

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 particul
...

Questions, Comments and Discussion

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