1、Information technology User interfaces Universal remote console Part 5: Resource description Technologies de linformation Interfaces utilisateur Console distance universelle Partie 5: Description des ressources INTERNATIONAL STANDARD ISO/IEC 24752-5 Reference number ISO/IEC 24752-5:2014(E) Second ed
2、ition 2014-12-15 ISO/IEC 2014 ii ISO/IEC 2014 All rights reserved COPYRIGHT PROTECTED DOCUMENT 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 photocopyi
3、ng, 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 office Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E
4、-mail copyrightiso.org Web www.iso.org Published in Switzerland ISO/IEC 24752-5:2014(E) ISO/IEC 24752-5:2014(E)Contents Page Foreword v Introduction vi 1 Scope . 1 2 Conformance . 1 3 Normative references 1 4 T erms and definitions . 2 5 Relation to other standards 2 5.1 Relation to Dublin Core Meta
5、data Element Set . 2 5.2 Relation to XML 2 6 Atomic resource description 3 6.1 General . 3 6.2 The about attribute . 3 6.3 The element 3 6.3.1 General 3 6.3.2 The xsi:type attribute 4 6.3.3 The xml:lang attribute 4 6.3.4 The element . 4 6.4 The element 5 6.5 The element 6 6.6 The element 6 6.7 The e
6、lement 7 6.7.1 General 7 6.7.2 The element 7 6.7.3 More examples for 11 6.8 The element 12 6.9 The element 12 6.10 The element .13 6.11 The element 13 6.12 The element .13 6.13 The element 14 6.14 The element . 14 6.15 The element 14 6.16 The element.15 6.17 Other elements from DCMI 15 ISO/IEC 2014
7、All rights reserved iii ISO/IEC 24752-5:2014(E)7 Resource sheet 15 7.1 General 15 7.2 The about attribute 17 7.3 The element .17 7.4 The element17 7.5 Other resource sheet properties from DCMI 18 7.6 The element 18 7.6.1 General.18 7.6.2 The element 18 7.6.3 The element 18 7.6.4 The element .18 7.6.
8、5 The element .19 7.6.6 The element .19 7.6.7 The element.19 7.6.8 Other resource sheet scents from DCMI .19 7.7 The element 19 7.7.1 General.19 7.7.2 Subelements of .19 7.8 Security considerations 19 8 Grouping resource 20 8.1 General 20 8.2 The about attribute 21 8.3 The element .21 8.4 The elemen
9、t 21 8.5 Elements from DCMI .22 8.6 The element .22 8.7 The element 22 8.8 The element 22 8.8.1 General.22 8.8.2 The element .22 9 Grouping sheet .25 9.1 General 25 9.2 The about attribute 26 9.3 The element .26 9.4 The element27 9.5 Other grouping sheet properties from DCMI .27 9.6 The element 27 9
10、.6.1 General.27 9.6.2 The element .28 9.6.3 The element .28 9.6.4 Other grouping sheet scents from DCMI 28 9.7 The element .28 9.7.1 General.28 9.7.2 Subelements of 28 9.8 Security considerations 28 Annex A (informative) Online resources for resource sheets and grouping sheets .29 Bibliography .30 i
11、v ISO/IEC 2014 All rights reserved ISO/IEC 24752-5: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 i
12、n 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 no
13、n-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 I
14、SO/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
15、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 o
16、f 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 a
17、s information about ISOs 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/TC JTC 1, Information technology, Subcommittee SC 35, User interfaces. This second edition
18、cancels and replaces the first edition (ISO/IEC 247525: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
19、: Target description Part 5: Resource description Part 6: Web service integration ISO/IEC 2014 All rights reserved v ISO/IEC 24752-5:2014(E) 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 i
20、n 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. This part of ISO/IEC 24752 defines a format for describing atomic resources, resource sheets, grouping resources, and grouping sheets re
21、levant to the user interface of a device or service (“target”). For atomic resources that are stored in a resource sheet, a storage format is specified. For atomic resources that are stored externally to the resource sheet, the pertinent format type specification applies. A resource is any object th
22、at is used as an entity or to support decision making in the construction of a concrete user interface. This part of ISO/IEC 24752 specifies how resources are described in the context of the universal remote console (URC) framework. It defines a format for describing atomic resources, resource sheet
23、s, grouping resources, and grouping sheets relevant to the user interface of a device or service (“target”). Atomic resources include text and non-text elements of a user interface such as labels, help text, keyboard shortcuts (access keys), associated words (keywords) and location text. Non-text el
24、ements may include icons, sounds or videos. Atomic resources can be characterized as follows. An atomic resource is of static nature, i.e. it does not change during the users interaction with the target. NOTE 1 This is not meant to exclude atomic resources that contain references (placeholders) to v
25、alues of socket variables. In this case the atomic resource itself (i.e. the static text with the reference to the socket variable) doesnt change, but its rendition may change when the targets state changes. An atomic resource can be of any form, including textual, visual, auditory, and multimodal.
26、This is reflected in the atomic resources type. Atomic resource types include text, sound, image, animation, and video clip. In this context animations and video clips are construed as static objects because they dont change over the user interfaces lifetime (the recorded bits of the video clip dont
27、 change when it is played). An atomic resource of type “Text” is modality-independent, i.e. it can be rendered in visual, auditory, or tactile forms. Atomic resources of types other than “Text” are modality-specific. An atomic resource is typically specific to the cultural, language, and functional
28、accommodation of a user. For example, textual atomic resources are typically language specific; images can be culture- specific; picture symbols can be used to represent concepts that can be understood by people with certain cognitive disabilities. An atomic resource can be replaced by a (supplement
29、al) resource (which is itself an atomic resource). Examples of atomic resources are the following: a text string used to label a window; a text string containing help for an interface element; an icon used to label a button; a Bliss symbol labelling a function; a sound file that announces help instr
30、uctions; a text string that describes how to locate an ATM in a public building. An atomic resource description specifies characteristics (as properties) of an atomic resource. Properties include its type, its use context, and the atomic resources storage location and format. The use context specifi
31、es the usage location (specific element in a specific user interface), usage role (e.g. label or help text), and language context pertaining to the application of an atomic resource.vi ISO/IEC 2014 All rights reserved ISO/IEC 24752-5:2014(E) An atomic resource can have more than one atomic resource
32、description, specifying additional properties and alternative property values, and several sets of use contexts. Also, atomic resource descriptions and the atomic resource they describe dont have to be stored in one file or on one server necessarily. For example, some atomic resources (e.g. images)
33、can be stored as binary files, and their descriptions are stored in text files. A grouping resource (or short grouping) specifies a hierarchical grouping of user interface elements that is external to a socket description. This part of ISO/IEC 24752 applies groupings to user interface socket element
34、s, but that is not a restriction in general. Groups of user interface (UI) elements can be nested, and subgroups and UI elements can occur multiple times within different groups. Groupings are structural hints as to how to present a concrete user interface made up of individual user interface elemen
35、ts, including user interface characteristics such as layout and navigation. Supplemental resources can replace or supplement the target resources. By choosing between a set of alternative objects when constructing the concrete user interface, the result can be tailored towards user preferences and u
36、ser device capabilities. The mechanism of supplemental resources facilitates the generation of specialized user interfaces that build on a common (modality-independent) user interface model, the user interface socket provided by the manufacturer of a target. A resource sheet is a file that contains
37、atomic resource descriptions of related atomic resources, plus optionally the atomic resources themselves (if they are textual). Alternatively (and for binary atomic resources) the atomic resources can be stored in individual files separate from the resource sheet. Typically, a manufacturer would pr
38、ovide one resource sheet per target and language. Third parties can provide additional resource sheets pertaining to the same target. See Annex A for a sample resource sheet. A grouping sheet is a file that contains groupings. Typically, a manufacturer would provide one grouping sheet per target in
39、a language-independent manner. Third parties can provide additional grouping sheets pertaining to the same target. See Annex A for a sample grouping sheet. One purpose of this part of ISO/IEC 24752 is to facilitate the development and deployment of a wide variety of devices (from different manufactu
40、rers) that can act as URCs. The URC framework and its components are specified in part 1, and the user interface socket in part 2 of this International Standard. A user interface socket is a machine-interpretable description of the state and functions of the target or a part of the target. The targe
41、t description is specified in ISO/IEC 24752-4. Within the URC framework, an atomic resource makes reference to a specific element in a user interface socket (described in a user interface socket description), to a specific element in a target description, or to any form of user interface implementat
42、ion description. NOTE 2 Within the URC framework, there needs to be a common set of resource types and a common format for resource descriptions so that they can be used by any URC. This part of ISO/IEC 24752 defines both. In this part of ISO/IEC 24752, the terms “resources” and “resource descriptio
43、ns” include only those objects and descriptions that conform to the International Standard formats defined in this part of ISO/IEC 24752. It is important to note that URCs can employ other types of resources and resource descriptions beyond those described in this part of ISO/IEC 24752. ISO/IEC 2014
44、 All rights reserved vii Information technology User interfaces Universal remote console Part 5: Resource 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 in
45、telligent agents. This part of ISO/IEC 24752 defines syntax and semantics for describing atomic resources, resource sheets, groupings, and grouping sheets relevant to the user interface of a device or service (“target”). 2 Conformance An extensible markup language (XML) fragment is an atomic resourc
46、e description in conformance with this part of ISO/IEC 24752 if it conforms to Clause 6. An atomic resource description may use language extensions if the extensions are coded in XML syntax, and if it follows the syntax and requirements outlined in this part of ISO/IEC 24752 for all of its non-exten
47、sion parts. An XML file is a resource sheet in conformance with this part of ISO/IEC 24752 if it conforms to Clause 7. A resource sheet may use language extensions if the extensions are coded in XML syntax, and if it follows the syntax and requirements outlined in this part of ISO/IEC 24752 for all
48、of its non-extension parts. An XML fragment is a grouping resource in conformance with this part of ISO/IEC 24752 if it conforms to Clause 8. A grouping resource may use language extensions if the extensions are coded in XML syntax, and if it follows the syntax and requirements outlined in this part
49、 of ISO/IEC 24752 for all of its non- extension parts. An XML file is a grouping sheet in conformance with this part of ISO/IEC 24752 if it conforms to Clause 9. A grouping sheet may use language extensions if the extensions are coded in XML syntax, and if it follows the syntax and requirements outlined in this part of ISO/IEC 24752 for all of its non-extension parts. NOTE URC manufacturers are encouraged to implement their URCs so that unrecogni
