ISO/IEC 24752-2:2014

Information technology — User interfaces — Universal remote console — Part 2: User interface socket description

ISO/IEC 24752-2:201j4 is a multi-part International Standard that aims to facilitate operation of information and electronic products through remote and alternative interfaces and intelligent agents. A user interface socket is an abstract user interface that describes the functionality and state of a device or service (target) in a machine-interpretable manner that is independent of presentation and input capabilities of a user interaction device. This part of ISO/IEC 24752 defines an Extensible Markup Language (XML)-based language for describing a user interface socket. The purpose of the user interface socket is to expose the relevant information about a target so that a user can perceive its state and operate it. This includes data presented to the user, variables that can be manipulated by the user, commands that the user can activate, and exceptions that the user is notified about. The user interface socket specification is applicable to the construction and adaptation of user interfaces.

Technologies de l'information — Interfaces utilisateur — Console à distance universelle — Partie 2: Description de "socket" d'interface utilisateur

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-2:2008 - Information technology — User interfaces — Universal remote console — Part 2: User interface socket description
• Effective Date: 04-Dec-2010

Standards Content (Sample)

INTERNATIONAL ISO/IEC
STANDARD 24752-2
Second edition
2014-12-15
Corrected version
2016-04-01
Information technology — User
interfaces — Universal remote
console —
Part 2:
User interface socket description
Technologies de l’information — Interfaces utilisateur — Console à
distance universelle —
Partie 2: Description de “socket” d’interface utilisateur
Reference number
©
ISO/IEC 2014
© ISO/IEC 2014, Published in Switzerland
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
Ch. de Blandonnet 8 • CP 401
CH-1214 Vernier, Geneva, Switzerland
Tel. [phone]
Fax [phone]
[e-mail]
www.iso.org
ii © ISO/IEC 2014 – All rights reserved

Contents Page
Foreword .vi
Introduction .vii
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 XPath expressions . 3
5.2.1 General. 3
5.2.2 Use of XPath 2.0 syntax and semantics . 3
5.2.3 The undefined value . 4
5.2.4 XPath functions . 4
5.2.5 Additional functions . 5
6 Structure of a socket description . 9
6.1 General . 9
6.2 The ‘about’ attribute .10
6.3 The ‘id’ attribute .10
6.4 The ‘sufficient’ attribute .10
6.5 The ‘complete’ attribute .10
6.6 The ‘extends’ attribute .11
6.7 The element.11
6.8 The element .12
6.9 Socket description properties from DCMI .12
6.10 , , , and elements .12
6.11 XSD type schema elements .12
6.12 Platform-specific mapping information for sockets .13
7 Sets .13
7.1 General .13
7.2 Attribute ‘id’ .13
7.3 Attribute ‘dim’ .13
7.4 Set dependencies .14
7.4.1 General.14
7.4.2 The dependency .15
7.4.3 The dependency .15
7.4.4 The dependency .15
7.5 Platform-specific mapping information for sets .15
7.6 Set properties from DCMI .16
7.7 Set members .16
8 Variables .16
8.1 General .16
8.2 The ‘id’ attribute .16
8.3 The ‘type’ attribute .16
8.3.1 General.16
8.3.2 Simple types .17
8.3.3 Space-Separated Value Lists.17
8.3.4 Comma-Separated Value (CSV) Lists .17
8.3.5 Stream types .17
8.3.6 Socket-internal types .18
8.3.7 Imported types .18
8.4 The ‘secret’ attribute .19
© ISO/IEC 2014 – All rights reserved iii

8.5 The ‘sensitive’ attribute .19
8.6 The ‘optional’ attribute .19
8.7 The ‘final’ attribute .20
8.8 The ‘dim’ attribute .20
8.9 Variable dependencies .21
8.9.1 General.21
8.9.2 The dependency .21
8.9.3 The dependency .22
8.9.4 The dependency .22
8.9.5 The dependency .23
8.9.6 The dependency .24
8.9.7 The dependency .24
8.9.8 The dependency .24
8.9.9 The dependency .25
8.9.10 The dependency .25
8.9.11 The dependency .26
8.9.12 The dependency .26
8.10 Selection.26
8.10.1 General.26
8.10.2 The ‘closed’ attribute.26
8.10.3 Static and dynamic selection sets .27
8.11 Platform-specific mapping information for variables .28
8.12 Variable properties from DCMI .28
9 Commands .28
9.1 General .28
9.2 The ‘id’ attribute .28
9.3 The ‘type’ attribute .29
9.3.1 General.29
9.3.2 uis:voidCommand .29
9.3.3 uis:basicCommand .29
9.3.4 uis:timedCommand .30
9.4 The ‘sensitive’ attribute .30
9.5 The ‘sufficient’ attribute .30
9.6 The ‘complete’ attribute .31
9.7 The ‘optional’ attribute .31
9.8 The ‘dim’ attribute .31
9.9 Command dependencies .32
9.9.1 General.32
9.9.2 The dependency .32
9.9.3 The dependency .33
9.9.4 The dependency .33
9.9.5 The dependency .34
9.10 Platform-specific mapping information for commands .34
9.11 Command properties from DCMI .35
9.12 Command parameters .35
9.12.1 General.35
9.12.2 The ‘id’ attribute (local parameter) .35
9.12.3 The ‘idref’ attribute (global parameter) .36
9.12.4 The ‘dir’ attribute .36
9.12.5 The ‘type’ attribute .37
9.12.6 The ‘secret’ attribute .37
9.12.7 The ‘sensitive’ attribute .37
9.12.8 The subelement .38
9.12.9 Platform-specific mapping information for command parameters .38
9.12.10 Command parameter properties from DCMI .38
10 Notifications .39
10.1 General .39
iv © ISO/IEC 2014 – All rights reserved

10.2 The ‘id’ attribute .39
10.3 The ‘type’ attribute .39
10.4 The ‘category’ attribute .41
10.5 The ‘sensitive’ attribute .41
10.6 The ‘optional’ attribute .41
10.7 The ‘dim’ attribute .41
10.8 The ‘timeout’ attribute .42
10.9 Notification dependencies .42
10.9.1 General.42
10.9.2 The dependency .43
10.10 Notification variables and commands .43
10.11 Platform-specific mapping information for notifications .44
10.12 Notification properties from DCMI .44
11 Type definitions .44
11.1 General .44
11.2 Facets .45
11.3 List of string values .45
11.4 Expressing structure within a type’s value space .46
11.5 Socket-internal types .46
11.6 Schema import .46
11.7 References to socket-external types .47
11.8 Element definitions .47
12 Security considerations.47
Annex A (informative) Documents for user interface socket descriptions .48
Bibliography .49
© ISO/IEC 2014 – All rights reserved v

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 24752-2:2008), which has been technically
revised.
This corrected version of ISO/IEC 24752-2:2014 incorporates the following modifications.
Clause 8: in the last line of paragraph 2 of 8.9.3, has been changed to and the
reference has been amended to 7.4.3 instead of 8.9.3.
Clause 11: in the EXAMPLE in 11.3, the spaces contained in the values of the value attribute have been
removed.
ISO/IEC 24752 consists of the following parts, under the general title Information technology — User
interfaces — Universal remote console:
— Part 1: General framework
— Part 2: User interface socket description
— Part 4: Target description
— Part 5: Resource description
— Part 6: Web service integration
vi © ISO/IEC 2014 – All rights reserved

Introduction
This is the second edition of this part of ISO/IEC 24752. 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 user interface socket is an abstract concept that, when implemented, exposes the functionality and
state of a target in a machine-interpretable manner. A user interface socket is independent of any
specific implementation platform.
A user interface socket contains variables, commands, and notifications, optionally structured in sets
that may be nested in a hierarchical fashion. The variables include all of the dynamic data a user can
perceive and/or manipulate, and may also include additional dynamic supporting data that is not
presented to the user. Example variables include the volume of a television, the current floor of an
elevator, or an internal variable representing the current state of a transaction that is used to control
dynamic features of the interface. A command is a core function that a user can request a target to
perform and that cannot be represented by a variable. The commands include all target functions that
can be called by users. Examples include the ‘search’ command of an airline reservation system or the
‘seek’ command of a CD player. A user interface socket does not include commands for accessing the
values of the variables. There are typically no commands that simply change the values of variables.
An exception would be a ‘reset’ operation which puts the target into a specific state. The notifications
are special states where normal operation is suspended, such as an exception state. Notifications are
special states triggered by the target. Examples include an announcement made by a public address
system in an airport, a clock alarm, or a response to invalid input for a field of a form.
A user interface socket specification is an XML document that uses the constructs defined in this part of
ISO/IEC 24752 to describe a user interface socket.
See Annex A for an example user interface socket description.
NOTE Additional information is needed before the socket can be presented to a user, including natural
language labels and help text associated with the elements of the user interface. This information is provided
externally to the socket description. Resources reference socket elements using the socket’s name (as given in
the socket descriptions ‘about’ attribute value, see 6.2) and the element ‘id’ attribute (see 7.2, 9.2 and 10.2). Refer
to ISO/IEC 24752-5 for further details.
© ISO/IEC 2014 – All rights reserved vii

INTERNATIONAL STANDARD ISO/IEC 24752-2:2014(E)
Information technology — User interfaces — Universal
remote console —
Part 2:
User interface socket description
1 Scope
ISO/IEC 24752 is a multi-part International Standard that aims to facilitate operation of information
and electronic products through remote and alternative interfaces and intelligent agents.
A user interface socket is an abstract user interface that describes the functionality and state of a
device or service (target) in a machine-interpretable manner that is independent of presentation
and input capabilities of a user interaction device. This part of ISO/IEC 24752 defines an Extensible
Markup Language (XML)-based language for describing a user interface socket. The purpose of the user
interface socket is to expose the relevant information about a target so that a user can perceive its state
and operate it. This includes data presented to the user, variables that can be manipulated by the user,
commands that the user can activate, and exceptions that the user is notified about. The user interface
socket specification is applicable to the construction and adaptation of user interfaces.
2 Conformance
An XML file conforms to this part of ISO/IEC 24752 (i.e. is a user interface socket description) if it fulfils
all of the following requirements:
a) it has an MIME type as specified in 6.1, if applicable;
b) it is coded in UCS (see 6.1);
c) its root element is the element (with uis representing the namespace “http://
openurc.org/ns/uisocketdesc-2”), as specified in Clause 6;
d) it contains all required elements and attributes with their proper values, as specified in Clause 6;
e) 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 socket 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 socket 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 15836:2009, Information and documentation — The Dublin Core metadata element set
© ISO/IEC 2014 – All rights reserved 1

ISO/IEC 10646:2011, Information technology — Universal Coded Character Set (UCS)
ISO/IEC 14977:1996, Information technology — Syntactic metalanguage — Extended BNF
ISO/IEC 24752-1, Information technology — User interfaces — Universal remote console — Part 1:
Framework
ISO/IEC 24752-4, Information technology — User interfaces — Universal remote console — Part 4: Target
description
W3C Recommendation: XML Path Language (XPath) 2.0 (Second Edition), W3C Recommendation 14
1)
December 2010 (Link errors corrected 3 January 2011)
W3C Recommendation: XQuery 1.0 and XPath 2.0 Functions and Operators (Second Edition), W3C
2)
Recommendation 14 December 2010
W3C Recommendation: XML Schema Part 1: Structures Second Edition, W3C Recommendation 28
3)
October 2004
W3C Recommendation: XML Schema Part 2: Datatypes Second Edition, W3C Recommendation 28
4)
October 2004
4 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO/IEC 24752-1 and
ISO/IEC 24752-4, and the following apply.
4.1
context element
element to which a dependency pertains
5 Relation to other standards
5.1 Relation to XML
This specification defines an extensible Markup Language (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 document with no namespace prefix are defined by
ISO/IEC 24752 series and are part of the namespace with URI reference http://openurc.org/ns/
uisocketdesc-2. If not defined as the default namespace, the namespace identifier ‘uis’ should be used.
Throughout this document, the following namespace prefixes and corresponding namespace identifiers
are used for referencing foreign namespaces:
— dc: The Dublin Core Metadata Element Set namespace (http://purl.org/dc/elements/1.1/) (Element
Set defined by ISO 15836);
1) File can be accessed in http://www.w3.org/TR/2010/REC-xpath20-20101214/
2) File can be accessed in http://www.w3.org/TR/2010/REC-xpath-functions-20101214/
3) File can be accessed in http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/
4) File can be accessed in http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/
2 © ISO/IEC 2014 – All rights reserved

— 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).
For an XML Schema definition for the user interface socket description see Annex A.
5.2 XPath expressions
5.2.1 General
This specification uses XML Path Language (XPath) Version 2.0 for addressing elements within the
socket. Specifically, XPath is used in describing dependencies between the elements of the socket.
XPath 2.0 syntax is used without XPath 1.0 compatibility.
5.2.2 Use of XPath 2.0 syntax and semantics
The ISO/IEC 24752 series uses the syntax and semantics of XPath 2.0, with the following additions and
exceptions:
a) The XPath expressions shall be coded in UCS.
b) The static expression context (see 2.1.1 in XPath 2.0) shall be initialized with the following
components:
1) “XPath 1.0 compatibility mode” shall be false.
2) The “statically known namespaces” are the namespace declarations that are in scope for he
XML element that contains the XPath expression.
3) The “default element/type namespace” shall be the null namespace (which refers to types that
are defined in the socket description, see Clause 11).
4) The “default function namespace” shall be the standard function namespace of XPath 2.0:
http://www.w3.org/2005/xpath-functions.
5) The “in-scope schema definitions” shall only contain “in-scope schema types” with the following
content: All types of namespace http://www.w3.org/2001/XMLSchema, as specified in section
2.5.1 of XPath 2.0; and the local types defined in a socket description’s part (see
Clause 11).
NOTE XPath 2.0 adds the following pre-defined types to the pre-defined types of XML Schema
Definition Part 2: xsd:untyped, xsd:untypedAtomic, xsd:anyAtomicType, xsd:dayTimeDuration,
xsd:yearMonthDuration.
6) The “in-scope variables” shall be empty.
7) The “function signatures” shall be the functions of the namespace http://www.w3.org/2005/
xpath-functions, as defined in XQuery 1.0 and XPath 2.0 Functions and Operators, with
exceptions as specified in 5.2.4 ; the constructor functions for all the atomic types in the “in-
scope schema definitions”; and the additional functions defined in 5.2.5.
NOTE The following components of the XPath 2.0 static expression context are not used in this part
of ISO/IEC 24752: “context item static type”, “statically known collations”, “default collation”, “base URI”,
“statically known documents”, “statically known collections”, “statically known default collection type”.
© ISO/IEC 2014 – All rights reserved 3

c) The dynamic expression context (see 2.1.2 in XPath 2.0) shall be initialized with the following
components:
1) The “context item” shall be the socket set or element that the XPath expression is specified for
as dependency.
2) The “variable values” shall be empty.
3) The “function implementations” shall include implementations of the functions of the
namespace http://www.w3.org/2005/xpath-functions, as defined in XQuery 1.0 and XPath 2.0
Functions and Operators; the constructor functions for all the atomic types in the “in-scope
schema definitions”; and the additional functions as defined in 5.2.5.
4) The “current dateTime” shall be the current time with local timezone of the URC, represented
as a value of type xsd:dateTime.
5) The “implicit timezone” shall be the local timezone of the URC.
NOTE The following components of the XPath 2.0 dynamic expression context are not used in this
part of ISO/IEC 24752: “context item”, “context position”, “context size”, “Available documents”, “Available
collections”, “Default collection”.
d) There is no Data Model (XDM instance). Expressions and functions that refer to a data model
instance shall not be used in socket descriptions. The context item expression (see 3.1.4 in XPath 2.0)
shall not be used. Path expressions (see 3.2 in XPath 2.0) shall not be used. Node operations such as
node comparison (see 3.5.3 in XPath 2.0), and the union, intersect and except operators (see 3.3.3
in XPath 2.0) shall not be used.
e) The evaluation of logical expressions (AND/OR) shall be strictly from left to right, and shall not
evaluate the right operand if the result is already determined by the left operand. I.e. with an
expression of the form “A and B”, B shall not be evaluated if A is false; and in the case of “A or B”,
B shall not be evaluated if A is true. In addition, Boolean operations shall respect the “undefined”
value (see 5.2.3).
f) The XPath 2.0 implementation shall be based on XML 1.0 and Namespaces in XML.
g) The XPath 2.0 implementation may support the namespace axis.
5.2.3 The undefined value
The ISO/IEC 24752 series adds the “undefined” value as a special value for all types from XPath 2.0 (see
5.2.2) and locally defined types (see Clause 11).
If any part of an XPath expression is undefined, the whole expression shall be undefined. This rule shall
not apply, if, based on evaluation logic, the result of an expression is determined without evaluating any
undefined part of it.
EXAMPLE The following expression will never evaluate to an undefined result. It yields true if the element
with id ‘myvar’ is available and has the value 4, otherwise it yields false.
uis:hasDefinedValue(‘myvar’) and uis:value(‘myvar’) eq 4

NOTE Implementations may vary as long as the described effect is warranted. For example, an error
exception could be internally raised to signal that an XPath expression yields “undefined”.
5.2.4 XPath functions
The following XPath functions may be used:
— Functions of the namespace http://www.w3.org/2005/xpath-functions, as defined in XQuery 1.0
and XPath 2.0 Functions and Operators
4 © ISO/IEC 2014 – All rights reserved

— The constructor functions for all atomic types in the “in-scope schema definitions”
with the following exceptions:
— The function string() shall only be used with one argument.
— The function resolve-uri() shall not be used.
— The functions related to QName (section 11 of XQuery 1.0 and XPath 2.0 Functions and Operators),
operators on NOTATION (section 13) and Functions and Operators on Nodes (section 14) shall not
be used.
— The following context functions (section 13 of XQuery 1.0 and XPath 2.0 Functions and Operators)
shall not be used: position, last, default-collation, static-base-uri.
The XPath 2.0 specific rules for implicit conversion between types apply.
5.2.5 Additional functions
5.2.5.1 General
The ISO/IEC 24752 series defines the following additional functions that may be used in expressing
socket dependencies.
NOTE These functions are defined in the namespace “http://openurc.org/ns/uisocketdesc-2”. A namespace
prefix for this namespace (e.g. “uis”) needs to be declared on any one of the XML elements containing the XPath
expression. Note that the namespace prefix for “http://openurc.org/ns/uisocketdesc-2” must always be used for
these functions since the default function namespace
...