ISO/IEC 24752-4:2014

Information technology — User interfaces — Universal remote console — Part 4: Target description

ISO/IEC 24752-4:2014 is a multi-part International Standard to facilitate operation of information and electronic products through remote and alternative interfaces and intelligent agents. ISO/IEC 24752-4:2014 defines an extensible markup language (XML) based language for the description of targets, as used within the universal remote console framework for discovery purposes. A document conforming to this language is a target description.

Technologies de l'information — Interfaces utilisateur — Console à distance universelle — Partie 4: Description d'objectifs

General Information

• Status: Withdrawn
• Publication Date: 11-Dec-2014
• Withdrawal Date: 11-Dec-2014
• ICS: 35.240.20 - IT applications in office work
• Technical Committee: ISO/IEC JTC 1/SC 35 - User interfaces
• Drafting Committee: ISO/IEC JTC 1/SC 35 - User interfaces
• Current Stage: 9599 - Withdrawal of International Standard
• Start Date: 22-Mar-2021
• Completion Date: 12-Feb-2026

Relations

• Revises: ISO/IEC 24752-4:2008 - Information technology — User interfaces — Universal remote console — Part 4: Target description
• Effective Date: 12-Nov-2011

Standards Content (Sample)

INTERNATIONAL ISO/IEC
STANDARD 24752-4
Second edition
2014-12-15
Information technology — User
interfaces — Universal remote
console —
Part 4:
Target description
Technologies de l’information — Interfaces utilisateur — Console à
distance universelle —
Partie 4: Description d’objectifs
Reference number
©
ISO/IEC 2014
© ISO/IEC 2014
All rights reserved. Unless otherwise specified, 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
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail [e-mail]
Web www.iso.org
Published in Switzerland
ii © ISO/IEC 2014 – All rights reserved

Contents Page
Foreword .v
Introduction .vi
1 Scope . 1
2 Conformance . 1
3 Normative references . 1
4 Terms and definitions . 2
5 Relation to other standards . 2
5.1 Relation to XML . 2
5.2 MIME type . 2
© ISO/IEC 2014 – All rights reserved iii

6 The element . 2
6.1 General . 2
6.2 The ‘about’ attribute . 3
6.3 The ‘id’ attribute . 3
6.4 The ‘hidden’ attribute . 3
6.5 The element. 4
6.6 The element . 4
6.7 Target properties from DCMI . 4
6.8 The element . 5
6.8.1 General. 5
6.8.2 The ‘type’ attribute . 5
6.8.3 The ‘id’ attribute . 5
6.8.4 Platform-specific mapping information . 5
6.8.5 The element . 6
6.9 The element . 6
6.9.1 General. 6
6.9.2 The ‘about’ attribute . 6
6.9.3 The element . 6
6.9.4 Other resource sheet properties from DCMI . 7
6.9.5 The element . . 7
6.9.6 The element . 8
6.10 The element . 8
6.10.1 General. 8
6.10.2 The ‘about’ attribute . 8
6.10.3 The element . 9
6.10.4 Other grouping sheet properties from DCMI . 9
6.10.5 The element . . 9
6.10.6 The element .10
6.11 The element .10
6.11.1 General.10
6.11.2 The ‘about’ attribute .10
6.11.3 The element .11
6.11.4 The element .11
6.11.5 Other UIID properties from DCMI .11
6.11.6 The element .11
6.12 The element .12
6.12.1 General.12
6.12.2 The ‘about’ attribute .12
6.12.3 The element .12
6.12.4 Other Resource Server properties from DCMI .13
6.13 The element .13
6.13.1 General.13
6.13.2 The ‘id’ attribute .13
6.13.3 The ‘name’ attribute . .13
6.13.4 The ‘type’ attribute .14
6.13.5 The ‘hidden’ attribute .14
6.13.6 The ‘maxSessions’ attribute .14
6.13.7 The ‘sharedSessions’ attribute .14
6.13.8 The ‘requestable’ attribute .15
6.13.9 The element .15
6.13.10 Socket properties from DCMI .15
6.13.11 Platform-specific mapping information for sockets.16
6.14 Platform-specific mapping information for the target .16
6.15 Security and privacy considerations .17
Annex A (informative) Online resources for target description .18
Bibliography .19
iv © ISO/IEC 2014 – 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. In the field of information technology, ISO and IEC have established a joint technical committee,
ISO/IEC JTC 1.
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).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation on the meaning of ISO specific terms and expressions related to conformity
assessment, as well as information about ISO’s adherence to the WTO principles in the Technical Barriers
to Trade (TBT), see the following URL: Foreword — Supplementary information.
The committee responsible for this document is ISO/IEC JTC 1, Information technology, Subcommittee
SC 35, User interfaces.
This second edition cancels and replaces the first edition (ISO/IEC 24752–4:2008), which has been
technically revised.
ISO/IEC 24752 consists of the following parts, under the general title Information technology — User
interfaces — Universal remote console:
— Part 1: Framework
— Part 2: User interface socket description
— Part 4: Target description
— Part 5: Resource description
— Part 6: Web service integration
© ISO/IEC 2014 – All rights reserved v

Introduction
This is the second edition of this part of the International Standard. The main purpose of the revision is an
alignment with recent developments in the Web service area, in particular with the new ISO/IEC 24752-
6 on Web service integration, along with an overall simplification of the specified technologies.
A target is a device or service that can be remotely accessed by a universal remote console (URC). All
targets provide exactly one target description (TD) through which they advertise their properties to
URCs during the discovery phase of a target-URC interaction. The TD provides the information needed
by a URC to connect to one of the target’s sockets in order to start a control session.
Target properties are network-independent characteristics of a target that are made available to any URC in
order to inform the user about the target’s purpose, and to provide references to resources and documents
that are needed to control the target via its sockets. The target description is independent of a natural
language. URCs need to consult the referenced resources in order to present this information to the user.
A target description (TD) is an extensible markup language (XML) document describing a target so
that it can be discovered by a URC. A TD contains references to XML documents, pertaining to specific
target sockets. These documents are: a user interface socket description (described in ISO/IEC 24752-
2), resource sheets (described in ISO/IEC 24752-5), grouping sheets (described in ISO/IEC 24752-5) and
user interface implementation descriptions (UIIDs) in any format.
vi © ISO/IEC 2014 – All rights reserved

INTERNATIONAL STANDARD ISO/IEC 24752-4:2014(E)
Information technology — User interfaces — Universal
remote console —
Part 4:
Target description
1 Scope
ISO/IEC 24752 is a multi-part International Standard to facilitate operation of information and electronic
products through remote and alternative interfaces and intelligent agents.
This part of ISO/IEC 24752 defines an extensible markup language (XML) based language for the
description of targets, as used within the universal remote console framework for discovery purposes.
A document conforming to this language is a target description.
2 Conformance
An XML file conforms to this part of ISO/IEC 24752 (i.e. is a target description) if it fulfils all of the
following requirements:
— it has an MIME type as specified in 5.2, if applicable;
— it is coded in UCS (see 6.1);
— its root element is the element (with td representing the namespace “http://openurc.
org/ns/targetdesc-2”), as defined in Clause 6;
— it contains all required elements and attributes with their proper values, as specified in Clause 6; and
— if it contains recommended or optional elements or attributes with their values, these are presented
as specified in Clause 6.
NOTE 1 Strict language conformance (i.e. no additional elements or attributes allowed) is not required because
future versions of this part of ISO/IEC 24752 might add new elements, attributes and values. Therefore, URC
manufacturers are encouraged to implement their URCs so that unrecognized markup is ignored without failing.
NOTE 2 Target manufacturers who want to add manufacturer-specific information to a target description
beyond the elements, attributes and values specified in this part of ISO/IEC 24752 can do so by externally providing
(proprietary) resource descriptions that point into the structure of a target description. Refer to ISO/IEC 24752—
5 for details.
3 Normative references
The following documents, in whole or in part, are normatively referenced in this document and are
indispensable for its application. For dated references, only the edition cited applies. For undated
references, the latest edition of the referenced document (including any amendments) applies.
ISO/IEC 10646:2012, Information technology — Universal Coded Character Set (UCS)
ISO/IEC 24752-1, Information technology — User interfaces — Universal remote console — Part 1: Framework
ISO/IEC 24752-2, Information technology — User interfaces — Universal remote console — Part 2: User
interface socket description
© ISO/IEC 2014 – All rights reserved 1

ISO/IEC 24752-5, Information technology — User interfaces — Universal remote console — Part 5:
Resource description
ISO 15836:2009, Information and documentation — The Dublin Core metadata element set
4 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO/IEC 24752-1 and
ISO/IEC 24752-2 apply.
5 Relation to other standards
5.1 Relation to XML
This specification defines an XML based language. Markup in XML is case sensitive.
Tag names, and attribute names, and values are not localizable, i.e. they are identical for all international
languages. However, the text content between tags can be language specific. As with all XML based
languages, white space characters immediately surrounding tags are non-significant.
This specification makes use of the XML namespaces concept to enable the import of element and
attribute names defined elsewhere.
All element and attribute names used in this International Standard with no namespace prefix are
defined by this International Standard and are part of the target description namespace with URI
reference “http://openurc.org/ns/targetdesc-2”. It is recommended to use the namespace identifier ‘td’
for it, if not defined as default namespace.
Throughout this International Standard, the following namespace prefixes and corresponding
namespace identifiers are used for referencing foreign namespaces:
— dc: The Dublin Core Metadata Element Set V1.1 namespace (http://purl.org/dc/elements/1.1/),
as specified in ISO 15836;
— dcterms: The DCMI Metadata Terms namespace (http://purl.org/dc/terms);
— xsd: The XML Schema namespace (http://www.w3.org/2001/XMLSchema);
— xsi: The XML Schema Instance namespace (http://www.w3.org/2001/XMLSchema-instance).
See Annex A for an XML Schema definition for the target description language.
5.2 MIME type
A target description shall have a MIME type of “application/urc-targetdesc+xml”, if applicable
(as specified in IETF RFC 2046).
The ‘charset’ parameter (see IETF RFC 3023) should be used to specify the character encoding of the
target description. Its value shall be “utf-8” or “utf-16”. If the ‘charset’ parameter is absent, the procedure
specified in “Extensible Markup Language (XML) 1.0 (Fifth Edition)”, section 4.3.3 shall be followed to
determine the character encoding.
6 The element
6.1 General
A target description shall be an XML document, and shall be coded in UCS according to ISO/IEC 10646.
For character encoding, “UTF-8” or “UTF-16” shall be used.
2 © ISO/IEC 2014 – All rights reserved

It shall have a single root element .
EXAMPLE A simple target description. Ellipses (“…”) indicate omissions.
xmlns:td=”http://openurc.org/ns/targetdesc-2”
about=”http://example.com/thermostat”
id=”target”>
…

Typically the element has a namespace definition attached to declare the namespace for
the target description, which is “http://openurc.org/ns/targetdesc-2”. It is recommended to use the
identifier ‘td’ for it, if it is not the default namespace.
NOTE There is no label or other natural-language information contained in . is an “anchor”
for attaching language-dependent descriptions that are stored as target resources or supplemental resources.
Resources (either referenced in the TD or provided by external resource services) pertaining to a
element have specific roles, including: label, help (with arbitrary help categories), access key, keyword, location.
Refer to part 5 of this International Standard for details on how to define atomic resources.
See Annex A for a sample target description. The following subsections describe the attributes and
elements of .
6.2 The ‘about’ attribute
The element shall have an ‘about’ attribute, and its value shall be a Uniform Resource Identifier
(URI), as specified in IETF RFC 3986.
The value of the ‘about’ attribute shall be the globally unique identifier (URI) of the target that is being
described in the target description. The URI may or may not be resolvable.
NOTE 1 Target manufacturers are encouraged to make the target descriptions of their products publicly
available by posting the target description at the target’s name URI.
NOTE 2 The target’s URI is provided by the target manufacturer. Typically the same URI is used for a class of
identical targets (products), disregarding their specific instance and location.
6.3 The ‘id’ attribute
The element shall have an ‘id’ attribute, and its value shall be a string. It shall be unique among
all ‘id’ attributes within the target description.
NOTE 1 The about and ‘id’ attributes are used to attach resources to the element.
NOTE 2 An atomic resource can be used to provide a location description for a target (see ISO/IEC 24752–5).
6.4 The ‘hidden’ attribute
The element may have a ‘hidden’ attribute, and its value shall be a Boolean (i.e. either “true” or
“false”). The default value shall be “false”.
A value of “true” is a hint to the URC that this target should not be shown to the user. However, it is
available to the user if referenced explicitly, for example when another target forwards a URC to the
hidden target.
This attribute is motivated by the desire not to overload the user with targets and sockets that they may
not need to know about during discovery. Hidden targets are not supposed to be visible to a user, unless
the user specifically requests to see them. However, hidden targets can still be accessed by the URC, for
example when another socket forwards the URC to the hidden target.
© ISO/IEC 2014 – All rights reserved 3

Additionally, during discovery the ‘hidden’ status of a target may be provided by the underlying network
in an implementation-dependent fashion. This is to relieve the URCs so that it is not burdened with
retrieving and parsing the TD of a ‘hidden’ target that it is not interested in.
NOTE The ‘hidden’ attribute can be specified on target and socket level. The socket inherits the setting from
the target. If specified on both levels, the socket’s ‘hidden’ attribute overrides the one of the target.
6.5 The element
The element shall have a subelement that specifies a reference to an
established standard to which the target conforms. The value, a URI (as specified in IETF RFC 3986),
is provided as element content. The value “http://openurc.org/ns/targetdesc-2/isoiec24752-4-2013”
indicates that the described target conforms to this International Standard.
EXAMPLE http://openurc.org/ns/targetdesc-2/isoiec24752-4-2013 dcterms:conformsTo>
NOTE 1 The value of the element can be used when testing for conformance of a
target description.
NOTE 2 The element is taken from the set of Dublin Core Metadata Terms.
6.6 The element
The element may have a subelement , indicating that the TD has been
modified from its original version, while still bearing the same target URI (see 6.2). Its content shall be
of type xsd:date or xsd:dateTime.
EXAMPLE 2003-12-30
NOTE 1 The element is taken from the set of Dublin Core Metadata Terms.
A target description should remain stable wherever possible. A TD that is changed shall be assigned a
new URI (see 6.2) or a new value for the element.
NOTE 2 This mechanism supports caching and facilitates the longevity of the target description and
supplemental resources.
6.7 Target properties from DCMI
Any element and element refinement from the set of Dublin Core Metadata Initiative (DCMI) Metadata
Terms may be used to describe a target, if appropriate (as specified in ISO 15836). Each of them may occur
multiple as child of the element. In particular, the following DCMI terms may be applied to a target:
— specifying the product code (or instance code) of the target;
— specifying the manufacturer of the target;
— specifying the provider of the target;
— specifying co-manufacturers of the target.
The ‘xsi:type’ attribute should be used to identify the coding schema, if appropriate.
EXAMPLE An identifier according to a specific identification schema:
0123456
4 © ISO/IEC 2014 – All rights reserved

6.8 The element
6.8.1 General
The element may have one or more subelements, each containing functional location
information (interpreted by the URC). The purpose is to let the user activate a function on the target that
helps them to locate the target.
EXAMPLE Examples include audio functions such as a beep or bell, visual functions such as a flash, and
direction based functions such as an “infrared ping” function.




NOTE There is no natural-language information contained in . This element is just the “anchor” for
attaching language-dependent descriptions that are stored as target resources or supplemental resources.
6.8.2 The ‘type’ attribute
The ‘type’ attribute shall be present in every element, and its value shall be either “audio”,
“visual” or “other”.
The meaning of the type value shall be as follows:
— “audio”: Audible locator, i.e. the target emits an audible signal (such as a beep or bell) when invoked
from the URC;
— “visual”: Visual locator, i.e. the target emits a visual signal (such as a flash) when invoked from the URC;
— “other”: Other means for localizing a target, e.g. IR pulse.
NOTE For type “other”, more specific information can be provided through the subelement (see
section 6.8.5).
6.8.3 The ‘id’ attribute
The element shall have an ‘id’ attribute which shall be unique among all ‘id’ attributes within
the target description. It is used to attach resources to the element, and to identify the specific
locator function when invoked on the target by a URC.
6.8.4 Platform-specific mapping information
The element may have one or more subelements to include platform-specific
mapping information.
The element shall have a ‘platform’ attribute whose value is not restricted by this
International Standard.
A element may have arbitrary element content and subelements. However, subelements
shall be from namespaces other than the namespace “http://openurc.org/ns/targetdesc-2”.
NOTE 1 Target descriptions that contain platform specific mapping information lose their platform neutrality.
Although multiple mappings may be specified in a target description (one for each platform) it is recommended
to consider other mechanisms of specifying the binding to platform-specific technologies. For example, mapping
information may be provided in an external file with references to the elements of the target description.
NOTE 2 Vendors and platform carriers are strongly discouraged from using the element for
embedding active or executable content in a target description. This would introduce a security risk for
components parsing such a target description, and executing such content.
© ISO/IEC 2014 – All rights reserved 5

6.8.5 The element
The element may have one or more subelements with each being a container for
vendor-specific extension elements from any namespace other than the namespace “http://openurc.
org/ns/targetdesc-2”. This International Standard does not define the processing of these elements.
NOTE 1 By restricting vendor-specific extensions to specified elements, target descriptions can be strictly
validated against an XML Schema Definition (see Annex A).
NOTE 2 Vendors are strongly discouraged from using the element for embedding active or
executable content in a target description. This would introduce a security risk for components parsing such a
target description, and executing such content.
6.9 The element
6.9.1 General
The element may have any number of subelements, each giving a reference to a
resource sheet provided by the target manufacturer, and available within a local network.
NOTE 1 Resource sheets are collections of atomic resources, as defined in part 5 of this International Standard.
A resource sheet referenced in this way may contain atomic resources for one or more sockets of the
target, as well as for the target itself (e.g. target label).
EXAMPLE

http://openurc.org/isoiec24752-5/2013
English resource sheet for Thermostat connected via
Wi-Fi
OpenURC Alliance
basic-thermostat1.0.en.rsheet

Text
http://openurc.org/res/devices/basic-thermostat.uis
en


NOTE 2 The element offers a possibility for a target manufacturer to provide “default” resource
sheets in a local network. Other resource sheets — which are possibly more suitable for specific use contexts —
can be retrieved from a resource server (see 6.12) provided by the target manufacturer or by third parties.
6.9.2 The ‘about’ attribute
The element shall have an ‘about’ attribute specifying an unambiguous identifier of the resource
sheet. This shall be a globally unique identifier in the form of a Uniform Resource Identifier (URI, as specified
in IETF RFC 3986), with no fragment identifier appended. This URI may or may not be resolvable.
NOTE 1 The ‘about’ attribute corresponds to the ‘about’ attribute on the element in a resource
sheet (see ISO/IEC 24752–5), although of a different namespace.
NOTE 2 The URI provided by the ‘about’ attribute may or may not be resolvable. In any case, use the URI
provided by (see 6.9.6) for retrieving the resource sheet.
NOTE 3 The identifier as a value of the ‘about’ attribute conforms to the Dublin Core metadata element
identifier, http://purl.org/dc/elements/1.1/identifier
6.9.3 The element
The element shall have one or more subelements, each specifying
a reference to an established standard to which the resource sheet and its contents (atomic resource
6 © ISO/IEC 2014 – All rights reserved

descriptions) conform. The value of each element shall be a URI (as specified in
IETF RFC 3986), and shall be provided as element content.
EXAMPLE The following code specifies that the resource sheet complies with part 5 of this International
Standard, of 2013:
http://openurc.org/isoiec24752-5/2013
NOTE 1 The element corresponds to the element as subelement
of in a resource sheet (see ISO/IEC 24752–5).
NOTE 2 The value of the element can be used when testing for conformance of a
resource sheet.
NOTE 3 conforms to the Dublin Core metadata element refinement conformsTo,
http://purl.org/dc/terms/conformsTo which is a refinement of the Dublin Core element http://purl.org/dc/
elements/1.1/relation
6.9.4 Other resource sheet properties from DCMI
The element may have any number of elements and element refinements from Dublin Core
Metadata Terms (see ISO 15836) as subelements, if appropriate, to describe the resource sheet. Each of
them may occur multiple times.
In particular, the following Dublin Core Metadata terms may occur:
—
—
—
—
— (with optional ‘xml:lang’ attribute)
6.9.5 The element
The element may have a subelement.
If present, the element may have any number of subelements, providing hints as to what the
resource sheet contains. The presence of each of these scent elements indicates that the scent value
applies to at least one atomic resource in the resource sheet. The same scent elements may hereby occur
multiple times, but with different values.
Applicable scent elements are the subelements of the element under in a resource
sheet, with their pertinent values given as element content (see ISO/IEC 24752–5). However, subelements
of the namespace “http://openurc.org/ns/rsheet-2” are hereby imported into the namespace “http://
openurc.org/ns/targetdesc-2”. Subelements of other namespaces keep their original namespace.
Applicable scent elements include:
—
—
— (namespace “http://openurc.org/ns/targetdesc-2”)
— (namespace “http://openurc.org/ns/targetdesc-2”)
—
— (of namespace “http://openurc.org/ns/targetdesc-2”)
© ISO/IEC 2014 – All rights reserved 7

— Other resource sheet scents from DCMI
6.9.6 The element
The element shall have one or more subelements.
Each element specifies a URI (as specified in IETF RFC 3986), given as element content,
that can be used to retrieve a copy of the referenced resource sheet, either from a server in a local or
global network environment.
If multiple elements are given, their order is significant for retrieving the resource
sheet. At runtime, the URIs will be tried in the order of the elements, and after a URI
has been found that successfully retrieves a document, the remaining URIs will be ignored.
NOTE 1 The target vendor/integrator can choose whether they want to serve resource sheets from a local
or global server. Local serving has the advantage of being independent of Internet connectivity. Global serving
usually involves a Web server dedicated to a vendor’s products, which can be easily updated. It is recommended
to provide both a global URI (for latest updates) and a local URI (as a fallback for offline situations).
Each URI may be relative, in which case it is based on a URI that is explicitly provided by the target in a
platform-specific way, or based on the URI of the containing document.
NOTE 2 When used in a target description (TD), relative URIs keep the TD clean of dependencies on a particular
networking platform and transport mechanism for retrieving the documents. The only part that has to be platform
specific is the fetch mechanism (URI) for the TD.
6.10 The element
6.10.1 General
The element may have any number of subelements, each giving a reference to a
grouping sheet provided by the target manufacturer, and available within a local network.
NOTE 1 A grouping sheet is a collection of grouping resources, as defined in part 5 of this International Standard.
A grouping sheet referenced in this way may contain groupings for one or more sockets of the target.
EXAMPLE

http://openurc.org/isoiec24752-5/2013
Grouping sheet for Thermostat connected via Wi-Fi
URC Consortium
basic-thermostat1.0.gsheet

http://openurc.org/res/devices/basic-thermostat.uis



NOTE 2 The element offers a possibility for a target manufacturer to provide “default” grouping
sheets in a local network. Other grouping sheets — which are possibly more suitable for specific use contexts —
can be retrieved from a resource server (see 6.12) provided by the target manufacturer or by third parties.
6.10.2 The ‘about’ attribute
The element shall have an ‘about’ attribute, specifying an unambiguous identifier of a
grouping sheet. This shall be a globally unique identifier in the form of a Uniform Resource Identifier
(URI), as specified in IETF RFC 3986, with no fragment identifier appended.
NOTE 1 The ‘about’ attribute corresponds to the ‘about’ attribute on the element in a grouping
sheet (see ISO/IEC 24752–5), although of a different namespace.
8 © ISO/IEC 2014 – All rights reserved

NOTE 2 The URI provided by the ‘about’ attribute may or may not be resolvable. In any case, use the URI
provided by (see 6.10.6) for retrieving the grouping sheet.
NOTE 3 The identifier as a value of the ‘about’ attribute conforms to the Dublin Core metadata element
identifier, http://purl.org/dc/elements/1.1/identifier
6.10.3 The element
The element shall have one or more subelements, each specifying a
reference to an established standard to which the grouping sheet and its contents (groupings) conform.
The value of each element shall be a URI (as specified in IETF RFC 3986), and
shall be provided as element content.
EXAMPLE The following code specifies that the grouping resource complies to part 5 of this International
Standard, as of 2012:
http://openurc.org/ns/gsheet-2/isoiec24752-5-2013
NOTE 1 The element corresponds to the element as subelement
of in a grouping sheet (see ISO/IEC 24752–5).
NOTE 2 The value of the element can be used when testing for conformance of a
grouping sheet.
NOTE 3 conforms to the Dublin Core metadata element refinement conformsTo,
http://purl.org/dc/terms/conformsTo which is a refinement of the Dublin Core element http://purl.org/dc/
elements/1.1/relation
6.10.4 Other grouping sheet properties from DCMI
The element may have any number of elements and element refinements from Dublin Core
Metadata Terms (see ISO 15836) as subelements, if appropriate, to describe the resource sheet. Each of
them may occur multiple times.
In particular, the following Dublin Core Metadata terms may occur:
—
—
—
—
— (with optional ‘xml:lang’ attribute)
6.10.5 The element
The element may have a subelement.
If present, the element may have any number of subelements, providing hints as to what the
grouping sheet contains. The presence of each of these scent elements indicates that the scent value
applies to at least one grouping in the grouping sheet. The same scent elements may hereby occur
multiple times, but with different values.
Applicable scent elements are the subelements of the element under in a grouping
sheet, with their pertinent values given as element content (see ISO/IEC 24752–5). However, subelements
of the namespace “http://openurc.org/ns/gsheet-2” are hereby imported into the namespace “http://
openurc.org/ns/targetdesc-2”. Subelements of other namespaces keep their original namespace.
Applicable scent elements include:
— (namespace “http://openurc.org/ns/targetdesc-2”);
© ISO/IEC 2014 – All rights reserved 9

— (namespace “http://openurc.org/ns/targetdesc-2”);
— other grouping sheet scents from DCMI.
6.10.6 The element
The element shall have one or more subelements.
Each element specifies a URI (as specified in IETF RFC 3986), given as element content,
that can be used to retrieve a copy of the referenced grouping sheet, either from a server in a local or
global network environment.
If multiple elements are given, their order is significant f
...