1、Information technology User interfaces Universal remote console Part 2: User interface socket description Technologies de linformation Interfaces utilisateur Console distance universelle Partie 2: Description de “socket” dinterface utilisateur INTERNATIONAL STANDARD ISO/IEC 24752-2 Reference number
2、ISO/IEC 24752-2:2014(E) Second edition 2014-12-15 ISO/IEC 2014 Corrected version 2016-04-01 ii ISO/IEC 2014 All rights reserved COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2014, Published in Switzerland All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utiliz
3、ed 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 ISOs member body in the country of the requester. ISO copyright
4、 office Ch. de Blandonnet 8 CP 401 CH-1214 Vernier, Geneva, Switzerland Tel. +41 22 749 01 11 Fax +41 22 749 09 47 copyrightiso.org www.iso.org ISO/IEC 24752-2:2014(E) ISO/IEC 24752-2:2014(E)Foreword vi Introduction vii 1 Scope . 1 2 Conformance . 1 3 Normative references 1 4 T erms and definitions
5、. 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
6、 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 element11 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
7、 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
8、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 Lists17 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 ty
9、pes .18 8.4 The secret attribute .19 ISO/IEC 2014 All rights reserved iii Contents Page ISO/IEC 24752-2:2014(E)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
10、.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
11、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:basicComman
12、d 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 .
13、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
14、.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 rig
15、hts reserved ISO/IEC 24752-2:2014(E)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
16、 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 T ype definitions .44 11.1 General 44 11.2 Facets 45 11.3 List of string values 45 11.4 Expressing structure within a typ
17、es 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 considerations47 Annex A (informative) Documents for user interface socket descriptions .48 Bibliography .49 ISO/IEC 2014 All rights reserved v I
18、SO/IEC 24752-2:2014(E)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 St
19、andards 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 a
20、nd 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 particu
21、lar 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 doc
22、ument 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 w
23、ww.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 ISOs adherence to
24、 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 editi
25、on (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
26、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 Pa
27、rt 4: Target description Part 5: Resource description Part 6: Web service integration vi ISO/IEC 2014 All rights reserved ISO/IEC 24752-2:2014(E) 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 We
28、b 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
29、 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 perce
30、ive 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 dy
31、namic 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 s
32、eek 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
33、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 in
34、terface 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, includ
35、ing 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 sockets name (as given in the socket descriptions about attribute value, see 6.2) and the ele
36、ment 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 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 ai
37、ms 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
38、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 tar
39、get 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 constru
40、ction 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
41、root element is the element (with uis representing the namespace “h t t p :/ 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 attrib
42、utes 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 manufactur
43、ers 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 ex
44、ternally 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 applicati
45、on. 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 INTERNATIONAL ST ANDARD ISO/IEC 24752-2:2014(E) ISO/I
46、EC 2014 All rights reserved 1 ISO/IEC 24752-2:2014(E) 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:
47、 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 December 2010 (Link errors corrected 3 January 2011) 1) W3C Recommendation: XQuery 1.0 and
48、XPath 2.0 Functions and Operators (Second Edition), W3C Recommendation 14 December 2010 2) W3C Recommendation: XML Schema Part 1: Structures Second Edition, W3C Recommendation 28 October 2004 3) W3C Recommendation: XML Schema Part 2: Datatypes Second Edition, W3C Recommendation 28 October 2004 4) 4
49、T erms a nd definiti ons 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
