ISO/IEC 19788-7:2019

INTERNATIONAL ISO/IEC
STANDARD 19788-7
First edition
2019-04
Information technology — Learning,
education and training — Metadata
for learning resources —
Part 7:
Bindings
Technologies de l'information — Apprentissage, éducation et
formation — Métadonnées pour ressources d'apprentissage —
Partie 7: Liaisons
Reference number
©
ISO/IEC 2019
© ISO/IEC 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/IEC 2019 – All rights reserved

Contents Page
Foreword .v
Introduction .vi
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 2
4 Symbols and abbreviated terms . 6
5 IRIs/URIs for ISO/IEC 19788 entities. 7
5.1 MLR identifiers . 7
5.2 RFC 5141-based identifier for ISO/IEC 19788 standard identifiers . 8
5.3 HTTP URIs for MLR entities . 9
5.4 Non-linguistic persistent canonical HTTP URIs for MLR entities .10
5.4.1 MLR entities other than vocabulary terms .10
5.4.2 MLR vocabulary terms .11
5.4.3 Prefixes for MLR entities non-linguistic persistent canonical HTTP URIs .11
5.5 Linguistic persistent canonical HTTP URIs for MLR entities .11
5.5.1 General.11
5.5.2 Linguistic identifier for DESs .12
5.5.3 Linguistic identifier for RCs .15
5.5.4 Linguistic identifier for vocabularies .16
5.5.5 Linguistic identifier for vocabulary terms .16
5.5.6 Linguistic identifier for PRSs .17
5.5.7 Linguistic identifier for DEGSs .17
5.5.8 Linguistic identifier for APs .18
6 Data elements: From MLR to RDF .18
6.1 General .18
6.1.1 Data elements .18
6.1.2 From MLR to RDF: At a glance .20
6.1.3 Mapping of MLR literal content.20
6.1.4 Prefixes .21
6.2 Data element with literal content .21
6.2.1 Literal content data elements .21
6.2.2 Linguistic MLR data element .21
6.2.3 Non-linguistic data element .23
6.3 Data element with non-literal content .25
6.3.1 Non-literal content data elements .25
6.3.2 MLR data element .26
6.3.3 RDF 1.1 data model .26
6.3.4 Serialization using Turtle 1.1 concrete syntax .26
7 OWL ontology for the ISO/IEC 19788 series .27
7.1 General .27
7.2 OWL 2 DL ontology for the MLR: MLROnt .27
7.2.1 MLROnt ontology expressed using the Manchester syntax .27
7.2.2 Rendering of the MLROnt ontology .31
7.2.3 MLROnt class diagram .35
7.3 Localized versions of the MLROnt ontology .36
7.3.1 English localized version of the MLR ontology .36
7.3.2 French localized version of the MLR ontology .38
8 MLR record .40
8.1 General .40
8.2 RDF dataset encoding of an MLR record .40
8.3 Example: An MLR record and its TriG serialization .41
© ISO/IEC 2019 – All rights reserved iii

8.4 Application profile record .47
9 MLR vocabularies — SKOS .49
9.1 MLR vocabularies .49
9.2 SKOS binding .50
9.2.1 IRIs for vocabularies .50
9.2.2 IRIs for concepts in a vocabulary .50
9.3 From MLR vocabularies to SKOS .51
9.3.1 General.51
9.3.2 Example: The MLR vocabulary “ISO _IEC _19788 -5:2012: V0200” (A udience
role) .51
9.4 Extension of an MLR vocabulary .54
9.5 MLR vocabulary dataset.55
9.5.1 General.55
9.5.2 TriG representation of the MLR vocabulary dataset .56
Annex A (informative) Globally unique identifiers for resources .58
Annex B (normative) Canonical MLR identifiers .60
Annex C (informative) Description of a learning resource: An example .67
Annex D (informative) MLR identifiers and the Web architecture.87
Annex E (informative) Bounded description of a learning resource .91
Annex F (informative) Examples of SPARQL requests against the MLR vocabulary dataset .93
Annex G (informative) Interrelations of MLR with other metadata standards and within
MLR itself .105
Bibliography .111
iv © ISO/IEC 2019 – All rights reserved

Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that
are members of ISO or IEC participate in the development of International Standards through
technical committees established by the respective organization to deal with particular fields of
technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other
international organizations, governmental and non-governmental, in liaison with ISO and IEC, also
take part in the work.
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 document 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 and IEC 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) or the IEC
list of patent declarations received (see http: //patents .iec .ch).
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 Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 36, Information technology for learning, education and training.
A list of all parts in the ISO/IEC 19788 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.
© ISO/IEC 2019 – All rights reserved v

Introduction
The primary purpose of the ISO/IEC 19788 series is to facilitate: (1) the description of a learning
resource by providing a standards-based approach to the identification and specification of the
metadata elements required to describe a learning resource, e.g. as a metadata learning resource (MLR)
record; and (2) the search, discovery, acquisition, evaluation, and use of learning resources, for instance
by learners, instructors or automated software processes.
The ISO/IEC 19788 series is modularly structured with all subsequent parts corresponding to a
specified set of user requirements for the identification and specification of metadata elements having
a particular focus and intended use in the description of a learning resource. This includes categories of
metadata elements focused on technical perspectives, pedagogical aspects, availability and intellectual
property aspects, bindings, etc.
This document maps the different ISO/IEC 19788-1 constructs to machine readable/understandable
entities. This document also proposes global (non-linguistic) identifiers for MLR entities and localized
(linguistic) identifiers for the same MLR entities.
The primary purpose of the ISO/IEC 19788 series is to specify elements and their attributes for the
description of learning resources. This includes the rules governing the identification of data elements
and the specification of their attributes.
The ISO/IEC 19788 series provides data elements for the description of learning resources and
resources directly related to learning resources.
The ISO/IEC 19788 series provides principles, rules and structures for the specification of the
description of a learning resource; it identifies and specifies the attributes of a data element as well
as the rules governing their use. The key principles stated in ISO/IEC 19788-1 are informed by a
user requirements-driven context with the aim of supporting multilingual and cultural adaptability
requirements from a global perspective.
ISO/IEC 19788-1 is information technology neutral and defines a set of common approaches, i.e.
methodologies and constructs, which apply to the development of the subsequent parts of the ISO/
IEC 19788 series.
vi © ISO/IEC 2019 – All rights reserved

INTERNATIONAL STANDARD ISO/IEC 19788-7:2019(E)
Information technology — Learning, education and
training — Metadata for learning resources —
Part 7:
Bindings
IMPORTANT — All links that are in regular font and blue/underlined are true links. Any other
links (especially in courier font) should not be considered functional.
1 Scope
This document provides RDF mappings of the different MLR entities introduced in the MLR framework
(ISO/IEC 19788-1 and its amendment): data element specifications (DESs), resource classes (RCs), data
elements (DEs), application profiles (APs), MLR records and data element group specifications (DEGSs).
This document associates HTTP IRIs (linguistically neutral and linguistic) to conceptual MLR entities
denoted by MLR identifiers. This is needed for the management of MLR entities and their versions.
Moreover, this document provides excerpts of an OWL 2 DL ontology for the resource classes and data
element specifications (properties) introduced in the ISO/IEC 19788 series.
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 of 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 639-2, Codes for the representation of names of languages — Part 2: Alpha-3 code
1)
ISO 639-3, Codes for the representation of names of languages — Part 3: Alpha-3 code for comprehensive
coverage of languages
2)
ISO 3166-1, Codes for the representation of names of countries and their subdivisions — Part 1:
Country codes
3)
ISO 15924, Information and documentation — Codes for the representation of names of scripts
4)
ISO/IEC 11404, , Information technology — General-Purpose Datatypes (GPD)
5)
ISO/IEC 19788-1:2011, Information technology — Learning, education and training — Metadata for
learning resources — Part 1: Framework
ISO/IEC 19788-1:2011/Amd 1:2014, Information technology — Learning, education and training —
Metadata for learning resources — Part 1: Framework/Amendment 1
1) The name and contact information of the Registration Authority for this ISO 639-3 can be found at http: //www
.iso .org/mara.
2) Alpha-2 codes available at http: //www .iso .org/iso/country_codes/iso _3166 _code _lists/country _names _and
_code _elements .htm.
3) Codes available at http: //www .unicode .org/iso15924/codelists .html.
4) Freely available at http: //standards .iso .org/ittf/PubliclyAvailableStandards/index .html.
5) Freely available at http: //standards .iso .org/ittf/PubliclyAvailableStandards/index .html.
© ISO/IEC 2019 – All rights reserved 1

ISO/IEC 19788-2, Information technology — Learning, education and training — Metadata for learning
resources — Part 2: Dublin Core elements
ISO/IEC 19788-2:2011/Amd 1:2016, Information technology — Learning, education and training —
Metadata for learning resources — Part 2: Dublin Core elements/Amendment 1: Non-literal content value
data elements
ISO/IEC 19788-5:2012, Information technology — Learning, education and training — Metadata for
learning resources — Part 5: Educational elements
ISO/IEC 19788-8:2015, Information technology — Learning, education and training — Metadata for
learning resources — Part 8: Data elements for MLR records
6)
IETF BCP 47: 2009, Tags for Identifying Languages
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO/IEC 19788-1 and ISO/
IEC 19788-1:2011/Amd 1:2014 and the following apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
— IEC Electropedia: available at http: //www .electropedia .org/
— ISO Online browsing platform: available at http: //www .iso .org/obp
3.1
conceptual
the qualified entity captures the “essence” of an MLR entity defined in an ISO/IEC 19788
part and further versioned in later parts of ISO/IEC 19788 (e.g. in later editions, amendments or
corrigenda)
EXAMPLE 1 Conceptual DES.
EXAMPLE 2 Conceptual RC.
EXAMPLE 3 Conceptual vocabulary.
EXAMPLE 4 Conceptual vocabulary term.
Note 1 to entry: MLR entities are identified with MLR identifiers, and conceptual MLR entities are identified with
canonical MLR identifiers.
3.2
blank node
element from a blank node set (3.3)
Note 1 to entry: In an RDF graph (3.14) a blank node indicates the existence of a thing, without using an IRI (3.8)
or a literal (3.10) to denote it. A blank node may be thought of as referring to an anonymous resource.
Note 2 to entry: In concrete RDF syntaxes, when identified, blank node identifiers are locally scoped to their
container and are NOT persistent.
Note 3 to entry: The MLR standard does not use blank nodes. Each blank node is replaced by a globally unique IRI
(a Skolem IRI).
Note 4 to entry: In Turtle, a concrete syntax for RDF, blank nodes in triples are expressed as _: followed by a blank
node label (e.g. _:alice, _:0-34-abc).
6) See http://t ools.ietf .org/html/bcp47.
2 © ISO/IEC 2019 – All rights reserved

3.3
blank node set
infinite set disjoint from the set of all IRIs (3.8) and the set of all literals (3.10)
Note 1 to entry: Any blank node set, the set of all IRIs and the set of all literals are pairwise disjoint.
Note 2 to entry: No other conditions are imposed on a blank node set than being disjoint from IRIs and literals.
3.4
content negotiation
practice of providing multiple representations (3.20) available via the same URI
Note 1 to entry: Which representation is served depends on negotiation between the requesting agent and the
agent serving the representations.
[SOURCE: Architecture of the World Wide Web, Volume One. W3C Recommendation. Available from:
http: //www .w3 .org/TR/2004/REC -webarch -20041215/]
3.5
graph store
mutable container of RDF graphs (3.14) managed by a single service
Note 1 to entry: Graph stores are similar to RDF datasets (3.12), but unlike an RDF dataset, named graphs can be
added to or deleted from a graph store.
Note 2 to entry: A graph store can be viewed as a mutable RDF dataset.
[SOURCE: SPARQL 1.1 Update — W3C Recommendation 21 March 2013, Section 2. Available from: http:
//www .w3 .org/TR/2013/REC -sparql11 -update -20130321/]
3.6
information resource
resource which has the property that all of its essential characteristics can be
conveyed in a message
EXAMPLE The information content of the book “Turtle, Termites, and Traffic Jams” by Mitchel Resnick (ISBN
0-262-18162-2) is an information resource. However, the physical object “Turtle, Termites, and Traffic Jams” book
owned by Gilles Gauthier is not an information resource.
[SOURCE: Architecture of the World Wide Web, Volume One. W3C Recommendation. Available from:
http: //www .w3 .org/TR/2004/REC -webarch -20041215/]
3.7
Internationalized Resource Identifier
IRI
sequence of characters that conforms to the syntax defined in RFC 3987
Note 1 to entry: IRIs may be written on paper, read aloud, stored or transmitted digitally. The same IRI may be
represented in many different ways.
3.8
Internationalized Resource Identifier
IRI
Unicode/ISO/IEC 10646 string that conforms to the syntax defined in RFC 3987
Note 1 to entry: IRIs in the RDF abstract syntax MUST be absolute and MAY contain a fragment identifier.
Note 2 to entry: When IRIs are used in operations that are only defined for URIs, they must first be converted
according to the mapping defined in section 3.1 of RFC 3987. A notable example is retrieval over the HTTP
protocol. The mapping involves UTF-8 encoding of non-ASCII characters, %-encoding of octets not allowed in
URIs, and Punycode-encoding of domain names.
© ISO/IEC 2019 – All rights reserved 3

[SOURCE: RDF 1.1 Concepts and Abstract Syntax — W3C Recommendation 25 February 2014, Section
3.2. Available from: http: //www .w3 .org/TR/2014/REC -rdf11 -concepts -20140225/]
3.9
language-tagged string
literal (3.10) for which the third component is present
Note 1 to entry: Most concrete RDF syntaxes represent language-tagged strings without the datatype IRI because
it always equals http://www.w3.org/1999/02/22-rdf-syntax-ns#langString.
3.10
literal
entity comprising two or three elements:
— a lexical form, being a Unicode string, which should be in Normal Form C,
— a datatype IRI, being an IRI (3.8) identifying a datatype that determines how the lexical form maps
to a literal value, and
— if and only if the datatype IRI is http://www.w3.org/1999/02/22-rdf-syntax-
ns#langString, a non-empty language tag as defined by BCP 47. The language tag MUST be well-
formed according to section 2.2.9 of BCP 47
[SOURCE: RDF 1.1 Concepts and Abstract Syntax — W3C Recommendation 25 February 2014, Section
3.3. Available from: http: //www .w3 .org/TR/2014/REC -rdf11 -concepts -20140225/]
3.11
media type
metadata for a representation (3.20), as per IETF RFC 6838, that provides format specification and
preferred interpretation for the representation
EXAMPLE image/jpeg, image/svg+xml, text/plain, text/html, text/turtle, video/H264, application/
xhtml+xml, application/trig, application/ld+json, application/json, application/rdf_xml.
Note 1 to entry: Media types, also called Internet media types, were previously called MIME types when used
essentially for email sent through the SMTP protocol.
Note 2 to entry: Registry of Internet media type is available online at http: //www .iana .org/assignments/media
-types.
3.12
RDF dataset
collection of RDF graphs comprising of
— exactly one default graph, being an RDF graph (3.14), and
— zero or more named graphs
Note 1 to entry: The default graph does not have a name and MAY be empty.
Note 2 to entry: Each named graph is a pair consisting of an IRI (3.8) or a blank node (3.2) (the graph name), and
an RDF graph. Graph names are unique within an RDF dataset.
Note 3 to entry: Blank nodes can be shared between graphs in an RDF dataset.
Note 4 to entry: RDF datasets are non-mutable (immutable): adding or removing RDF triples or RDF graphs from
an RDF dataset yields a different RDF dataset.
Note 5 to entry: Despite the use of the word “name” in “named graph”, the graph name is not required to denote
the graph. It is merely syntactically paired with the graph. RDF does not place any formal restrictions on what
resource the graph name may denote, nor on the relationship between that resource and the graph.
[SOURCE: Adapted from RDF 1.1 Concepts and Abstract Syntax — W3C Recommendation 25 February
2014, Section 4. Available from: http: //www .w3 .org/TR/2014/REC -rdf11 -concepts -20140225/]
4 © ISO/IEC 2019 – All rights reserved

3.13
RDF document
document that encodes an RDF graph (3.14) or RDF dataset (3.12) in a concrete RDF syntax, such
as Turtle, RDFa, JSON-LD or TriG
Note 1 to entry: RDF documents enable the exchange of RDF graphs and RDF datasets between systems.
[SOURCE: RDF 1.1 Concepts and Abstract Syntax — W3C Recommendation 25 February 2014, Section
1.8. Available from: http: //www .w3 .org/TR/2014/REC -rdf11 -concepts -20140225/]
3.14
RDF graph
set of RDF triples (3.18)
Note 1 to entry: RDF graphs are non-mutable (immutable): adding or removing RDF triples from an RDF graph
yields a different RDF graph.
3.15
RDF node set
set of subjects and objects from all the RDF triples (3.18) of an RDF graph (3.14)
3.16
RDF source
persistent and mutable source or container for RDF graphs (3.14)
Note 1 to entry: An RDF source is a resource whose state can change over time.
Note 2 to entry: Examples of RDF sources are files containing a serialization of an RDF graph using a concrete
RDF syntax and triple stores (3.22).
[SOURCE: Adapted from RDF 1.1 Concepts and Abstract Syntax — W3C Recommendation 25 February
2014, Section 1.5. Available from: http: //www .w3 .org/TR/2014/REC -rdf11 -concepts -20140225/]
3.17
RDF term
IRI (3.8), literal (3.10) or blank node (3.2)
Note 1 to entry: IRIs, literals and blank nodes are distinct and distinguishable. For example, http://example.
org/ as a string literal is neither equal to http://example.org/ as an IRI, nor to a blank node with the blank
identifier http://example.org/.
[SOURCE: RDF 1.1 Concepts and Abstract Syntax — W3C Recommendation 25 February 2014, Section
3.1. Available from: http: //www .w3 .org/TR/2014/REC -rdf11 -concepts -20140225/]
3.18
RDF triple
entity consisting of three ordered components, namely
— the subject, which is an IRI (3.8) or a blank node (3.2),
— the predicate, which is an IRI, and
— the object, which is an IRI, a literal (3.10) or a blank node
Note 1 to entry: Any IRI denotes an entity in the world (the “universe of discourse”).
Note 2 to entry: Triples are written in the order subject, predicate, object.
[SOURCE: Adapted from RDF 1.1 Concepts and Abstract Syntax — W3C Recommendation 25 February
2014, Section 3.1. Available from: http: //www .w3 .org/TR/2014/REC -rdf11 -concepts -20140225/]
© ISO/IEC 2019 – All rights reserved 5

3.19
RDF vocabulary
collection of IRIs (3.8) intended for use in RDF graphs (3.14)
[SOURCE: RDF 1.1 Concepts and Abstract Syntax — W3C Recommendation 25 February 2014, Section
1.4. Available from: http: //www .w3 .org/TR/2014/REC -rdf11 -concepts -20140225/]
3.20
representation
data that encode information about resource state
Note 1 to entry: A resource may have more than one representation: The information resource “Turtle, Termites,
and Traffic Jams” by Mitchel Resnick (ISBN 0-262-18162-2) could have textual representations (plain text, HTML,
epub, portable document format (PDF), Microsoft Word, Braille, etc.), representations in various languages
(English, French, etc.), audio representations, etc.
Note 2 to entry: Metadata such as character encoding (e.g. UTF-8, UTF-16, US-ASCII, ISO-8859-1) or content
encoding (e.g. XML, HTML, JPEG video, JSON file) may be provided.
[SOURCE: Adapted from Architecture of the World Wide Web, Volume One. W3C Recommendation,
2004. Available from: http: //www .w3 .org/TR/2004/REC -webarch -20041215/]
3.21
simple literal
literal (3.10) for which the datatype IRI (3.8) is http://www.w3.org/2001/XMLSchema#string
Note 1 to entry: Most concrete syntaxes represent simple literals without the datatype IRI because it always
equals http://www.w3.org/2001/XMLSchema#string.
3.22
triple store
specialized database for the storage and retrieval of RDF triples (3.18)
Note 1 to entry: A triple store is an RDF source (3.16).
3.23
Web resource
information resource (3.6) that “lives on the World Wide Web”
Note 1 to entry: A Web resource can be denoted by an HTTP IRI and under normal conditions (server not down),
a representation of the resource (the exact representation retrieved might depend on content negotiation) can be
retrieved using that IRI and the HTTP protocol.
4 Symbols and abbreviated terms
AP Application Profile
DEGS Data Element Group Specification
DES Data Element Specification
FOAF Friend of a Friend
HTTP Hypertext Transfer Protocol
IRI Internationalized Resource Identifier
JSON JavaScript Object Notation
JSON-LD JavaScript Object Notation for Linking Data
6 © ISO/IEC 2019 – All rights reserved

MLR Metadata for Learning Resource
OWL Web Ontology Language
PRS Predefined Rule Set
PURL Persistent Uniform Resource Locator
RC Resource Class
RDF Resource Description Framework
SKOS Simple Knowledge Organization System
TriG RDF Dataset Language
Turtle Terse RDF Triple Language
URI Uniform Resource Identifier
VOC Vocabulary
W3C World Wide Web Consortium
XML Extensible Markup Language
5 IRIs/URIs for ISO/IEC 19788 entities
5.1 MLR identifiers
The ISO/IEC 19788 series makes available data element specifications (DESs), resource classes
(RCs), data element group specifications (DEGSs) and application profiles (APs). The ISO/IEC 19788
series assigns globally unique, persistent identifiers for those objects, as specified in the production
rules (see ISO/IEC 19788-1:2011, B.2).
7)
Examples of MLR identifier :
1) Data element specification (DES) from ISO/IEC 19788-2 (Dublin Core elements) —
ISO/IEC 19788-2:2011, 5.1:
ISO _IEC _19788 -2: 2011: : DES0100 (title)
2) Data element specification (DES) from ISO/IEC 19788-2 (Dublin Core elements) —
ISO/IEC 19788-2:2011/Amd 1:2016, 5.16:
ISO _IEC _19788 -2: 2011: AMD .1: 2015: : DES1600 (creator)
3) Resource class (RC) from ISO/IEC 19788-1 (Framework) —
ISO/IEC 19788-1:2011, 8.4.2:
ISO _IEC _19788 -1: 2011: : RC0002 (Learning Resource)
4) Predefined rule set (PRS) from ISO/IEC 19788-1 (Framework) —
ISO/IEC 19788-1:2011, 9.4:
ISO _IEC _19788 -1: 2011: : PRS0003 (Date & Time)
5) Data element group specification (DEGS) from ISO/IEC 19788-3 (Basic application profile) —
ISO/IEC 19788-3:2011, 6.1:
ISO _IEC _19788 -3: 2011: : DEGS0001 (MLR Basic data element group specification)
7) Terms between parentheses, e.g. (title), at the end of MLR identifiers are not part of the identifiers; they are only
provided to ease the reading of the present document.
© ISO/IEC 2019 – All rights reserved 7

6) Application profile (AP) from ISO/IEC 19788-3 (Basic application profile) —
ISO/IEC 19788-3:2011, Clause 5:
ISO _IEC _19788 -3: 2011: : AP0001 (MRL Basic Application Profile)
7) Vocabulary (V) from ISO/IEC 19788-5 (Educational elements) —
ISO/IEC 19788-5:2012, A.1:
ISO _IEC _19788 -5: 2012: : V0100 (Agent role)
NOTE  See B.7, Footnote 25.
8) Vocabulary term (T) from ISO/IEC 19788-5 (Educational elements) —
ISO/IEC 19788-5:2012, A.1:
ISO _IEC _19788 -5: 2012: : V0100: T020 (validator)
5.2 RFC 5141-based identifier for ISO/IEC 19788 standard identifiers
In the context of the World Wide Web and the Semantic Web, there is a need to have global identifiers
based on URIs for MLR identifiers. Fortunately, the ISO Central Secretariat has already published the
specification of a syntax for URNs that identifies documents developed (as per the ISO/IEC Directives)
by the International Organization for Standardization (ISO): RFC 5141 — A Uniform Resource Name
8)
(URN) for the International Organization for Standardization (ISO) .
RFC 5141 identifiers are globally unique, persistent and location-independent, and allow for the
identification of any clause from an ISO standard.
The ISO/IEC 19788 identifiers make use of only a subset of the RFC 5141: the part needed to identify the
ISO/IEC 19788 documents or resources extracted from such documents (for any of its parts, in any of
its editions, versions, amendments, corrigenda, etc.).
The RFC 5141 URN identifiers used in this document are constructed using the following production
rules (using the syntax of IETF RFC 5141):
9)
RFC5141_URN_Identifier = “urn:iso:std:iso-iec:19788” [“:” partnumber]
[[“:” status] “:” edition][“:” docversion]
10)
*supplement [addition ]
Table 1 provides examples of RFC 5141 URN for ISO/IEC 19788-related standards given in the first column.
8) RFC 5141: http: //tools.ietf .org/html/rfc5141.
9) The type, language and docelement constructs of RFC 5141 are not used in this document.
10) This document uses the following RFC 5141 production rules:
addition  = techdefined | isodefined
techdefined = “:tech” *techelement
techelement =
with the following exception: The part “:tech” of the “techdefined” construct is not used as no ambiguities
are introduced doing so and the resultings MLR identifiers are then more “natural”. This may be reviewed if
necessary.
8 © ISO/IEC 2019 – All rights reserved

Table 1 — RFC 5141 URN identifier of standard examples
RFC5141_URN_Identifier
Standard
ISO _IEC _19788 -2: 2011 urn:iso:std:iso-iec:19788:-2:ed-1
urn:iso:std:iso-iec:19788:-2:ed-1
ISO _IEC _19788 -2: 2011(E)
urn:iso:std:iso-iec:19788:-2:ed-1
ISO _IEC _19788 -2: 2011(F)
urn:iso:std:iso-iec:19788:-1:ed-1:amd:1
ISO/IEC 19788-1:2011/Amd 1:2014
urn:iso:std:iso-iec:19788:-1:ed-1:v1-amd1.v1
Document comprising the first edition
of the standard (ISO/IEC 19788-1:2011)
and incorporating its first amendment
(ISO/IEC 19788-1:2011/Amd 1:2014).
The RFC 5141 URN schema has been developed with the intent that a URN identifying an ISO document
item can be transformed to a valid HTTP URI by replacing the URN namespace prefix (“iso”) and the
“std:” prefix with the domain name “standards.iso.org”, replacing all occurrences of “:” within the
identifier with “/”, and converting characters to lower case.
Table 2 provides the RFC 5141 URI identifiers version of the previous table.
Table 2 — RFC 5141 URI identifiers for the standards of Table 1
RFC5141 URI Identifier
Standard
ISO _IEC_ 19788 -2: 2011 http://standards.iso.org/iso-iec/19788/-2/ed-1
ISO _IEC_ 19788 -2: 2011(E) http://standards.iso.org/iso-iec/19788/-2/ed-1
ISO _IEC_ 19788 -2: 2011(F) http://standards.iso.org/iso-iec/19788/-2/ed-1
ISO/IEC 19788-1:2011/Amd 1:2014 http://standards.iso.org/iso-iec/19788/-1/ed-1/amd/1
Document comprising the first edition http://standards.iso.org/iso-iec/19788/-1/ed-1/
of the standard (ISO/IEC 19788-1:2011) v1-amd1.v1
and incorporating its first amendment
(ISO/IEC 19788-1:2011/Amd 1:2014).
5.3 HTTP URIs for MLR entities
Given an MLR identifier (see B.1)
MLR_Identifier ::= Standard_ID “::” MLR_ID
MLR_ID ::= DES_ID | RC_ID | PRS_ID | DEGS_ID | AP_ID |
Vocabulary_ID | Vocabulary_Term_ID
for an MLR entity (either data element specification, resource class, predefined rule set, data element
group specification, application profile, vocabulary, or vocabulary term), an HTTP URI denoting
(identifying) the entity is given by
/
where is the RFC 5141 URI identifier version of the “Standard_ID” part of the
identifier of the MLR entity, and is the MLR_ID part of the identifier of the MLR entity (in
11)
which any “:” is replaced by a “#” and upper case letters changed to their lower case equivalent).
Examples of HTTP URI for MLR entities (using the examples provided in 5.1) are provided in Table 3.
11) This case only concerns identifier of vocabulary terms.
© ISO/IEC 2019 – All rights reserved 9

Table 3 — Examples of HTTP URI for MLR entities
MLR entity HTTP URI denoting the MLR entity
ISO _IEC _19788 -2: 2011: : DES0100 (title) http://standards.iso.org/iso-iec/19788/-2/ed-1/
a
des0100
ISO _IEC _19788 -2: 2011: AMD .1: 2015: : http://standards.iso.org/iso-iec/19788/-2/ed-1/
DES1600 (creator) amd/1/des1600
ISO _IEC _19788 -1: 2011: : RC0002 http://standards.iso.org/iso-iec/19788/-1/ed-1/rc0002
(Learning Resource)
ISO _IEC _19788 -1: 2011: : PRS0003 http://standards.iso.org/iso-iec/19788/-1/ed-1/prs0003
(Date & Time)
ISO _IEC _19788 -3: 2011: : DEGS0001 http://standards.iso.org/iso-iec/19788/-3/ed-1/
(MLR Basic data element group speci- degs0001
fication)
ISO _IEC _19788 -3: 2011: : AP0001 http://standards.iso.org/iso-iec/19788/-3/ed-1/ap0001
(MRL Basic Application Profile)
ISO _IEC _19788 -5: 2012: : V0100 http://standards.iso.org/iso-iec/19788/-5/ed-1/v0100
(Agent role)
ISO _IEC _19788 -5: 2012: : V0100: T020 http://standards.iso.org/iso-iec/19788/-5/ed-1/
(validator) v0100#t020
a
To be fully conformant to RFC 5141, this should be http://standards.iso.org/iso-iec/19788/-2/
ed-1/tech/des0100. See the note attached to the “addition” construct in 5.2. The same applies to all MLR
entities identifiers. We do not use “tech” in this document.
5.4 Non-linguistic persistent canonical HTTP URIs for MLR entities
5.4.1 MLR entities other than vocabulary terms
Consider an MLR identifier (see B.1) for an MLR entity that is either a data element specification, a
resource class, a predefined rule set, a data element group specification, an application profile or a
vocabulary).
MLR_Identifier ::= Standard_ID “::” MLR_ID
MLR_ID ::= DES_ID | RC_ID | PRS_ID | DEGS_ID | AP_ID | Vocabulary_ID
The non-linguistic persistent canonical HTTP URI denoting the MLR entity is composed of two parts
(separated by “/”): the first part concerning the identification of the standard involved and the second
part concerning the local identifier of the entity (in the context of the standard).
The first part is the HTTP form (see 5.3) of the RFC 5141 URI identifier of the canonical version (see
Annex B) of the “Standard_ID” part of the identifier of the MLR entity in which the string “standards.
iso.org” has been replaced by “purl.iso.org”, and the second part is the MLR_ID part of the
identifier of the MLR entity in which upper case letters have been changed to their lower case equivalent.
Table 4 presents examples of non-linguistic persistent canonical HTTP URI for MLR entities (using the
examples provided in 5.1).
Table 4 — Examples of non-linguistic persistent canonical HTTP URI for MLR entities
MLR entity Persistent canonical HTTP URI denoting the associated
conceptual MLR entity
ISO _IEC _19788 -2: 2011: : DES0100 (title) http://purl.iso.org/iso-iec/19788/-2/des0100
ISO _IEC _19788 -2: 2011: AMD .1: 2015: : http://purl.iso.org/iso-iec/19788/-2/des1600
DES1600 (creator)
ISO _IEC _19788 -1: 2011: : RC0002 http://purl.iso.org/iso-iec/19788/-1/rc
...