ISO IEC 24752-4-2014 Information technology - User interfaces - Universal remote console - Part 4 Target description《信息技术 用户接口 通用远程控制台 第4部分 目标描述(Target descript.pdf

1、Information technology User interfaces Universal remote console Part 4: Target description Technologies de linformation Interfaces utilisateur Console distance universelle Partie 4: Description dobjectifs INTERNATIONAL STANDARD ISO/IEC 24752-4 Reference number ISO/IEC 24752-4:2014(E) Second edition

2、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 photocopying, or

3、 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-mail

4、copyrightiso.org Web www.iso.org Published in Switzerland ISO/IEC 24752-4:2014(E) ISO/IEC 24752-4: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 XML 2 5.2 MIME type .

5、2 ISO/IEC 2014 All rights reserved iii ISO/IEC 24752-4:2014(E)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 attr

6、ibute 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 elem

7、ent 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 Othe

8、r 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

9、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 Platf

10、orm-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 ISO/IEC 24752-4:2014(E) Foreword ISO (the International Organization for Standardizat

11、ion) 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

12、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

13、 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 shou

14、ld 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 responsibl

15、e 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

16、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 the WTO principles in the Technical Barriers to Trade (TBT), see the following URL

17、 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 247524:2008), which has been technically revised. ISO/IEC 24752 consist

18、s 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 IS

19、O/IEC 24752-4: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 in the Web service area, in particular with the new ISO/IEC 24752- 6 on Web service integration, along with an overall s

20、implification 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 int

21、eraction. The TD provides the information needed by a URC to connect to one of the targets 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 targets purpose, and

22、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 extensi

23、ble 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/

24、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 Information technology User interfaces Universal remote console Part 4: Target description 1 Scope ISO/IEC 24752 is a multi-part Inter

25、national 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

26、 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 appl

27、icable; it is coded in UCS (see 6.1); its root element is the element (with td representing the namespace “h t t p :/o p e nu r c . 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 r

28、ecommended 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, attribut

29、es 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 thi

30、s 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

31、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, I

32、nformation 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 INTERNATIONAL ST ANDARD ISO/IEC 24752-4:2014(E) ISO/IEC 2014 All rights reserved 1 ISO/IEC 24752

33、4:2014(E) 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 T erms a nd definiti ons For the purposes of this document, the terms and definitions given in

34、 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. Ho

35、wever, 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. A

36、ll 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 “h t t p :/o p e nu r c . org/ns/targetdesc-2”. It is recommended to use the namespace identifier

37、 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 (h t t p :/p u r l . org/dc/elements/

38、1.1/), as specified in ISO 15836; dcterms: The DCMI Metadata Terms namespace (h t t p :/p u r l . 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 defin

39、ition 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 descriptio

40、n. 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 docume

41、nt, 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 ISO/IEC 24752-4:2014(E) It shall have a single root element . EXAMPLE A simple target description. Ellipses (“”) indicate omissions.Typically the ele

42、ment has a namespace definition attached to declare the namespace for the target description, which is “h t t p :/o p e nu r c . 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 c

43、ontained 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 arbitr

44、ary 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 shal

45、l 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.

46、NOTE 1 Target manufacturers are encouraged to make the target descriptions of their products publicly available by posting the target description at the targets name URI. NOTE 2 The targets URI is provided by the target manufacturer. Typically the same URI is used for a class of identical targets (p

47、roducts), 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

48、element. NOTE 2 An atomic resource can be used to provide a location description for a target (see ISO/IEC 247525). 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

49、 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