1、Information technology User interfaces Universal remote console Part 6: Web service integration Technologies de linformation Interfaces utilisateur Console distance universelle Partie 6: Intgration du service web INTERNATIONAL STANDARD ISO/IEC 24752-6 Reference number ISO/IEC 24752-6:2014(E) First e
2、dition 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 photocopy
3、ing, 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
4、E-mail copyrightiso.org Web www.iso.org Published in Switzerland ISO/IEC 24752-6:2014(E) ISO/IEC 24752-6:2014(E)Contents Page Foreword iv Introduction v 1 Scope . 1 2 Conformance . 1 3 Normative references 3 4 T erms and definitions . 3 5 Relation to other standards 4 5.1 Relation to XML 4 6 Mapping
5、 Descriptions . 4 6.1 General . 4 6.2 Mapping a target to a Web service . 5 6.3 Mapping a socket to a Web service partition 5 6.4 Mapping a socket variable . 6 6.5 Mapping a socket command 7 6.6 Mapping a socket notification 8 6.7 Mapping a socket-internal type definition to a Web services type defi
6、nition 8 7 Embedding target description and socket descriptions in a WSDL document9 7.1 General . 9 7.2 Restriction on target namespaces of internal schema part 9 7.3 Restriction on identifiers within target and socket descriptions 9 7.4 name attribute values . 9 7.5 Implicit target description .10
7、7.6 Implicit socket description 20 7.7 Resources 63 Annex A (informative) Example documents for a digital thermostat .64 Bibliography .65 ISO/IEC 2014 All rights reserved iii ISO/IEC 24752-6:2014(E) Foreword ISO (the International Organization for Standardization) and IEC (the International Electrot
8、echnical 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
9、 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
10、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 i
11、n 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
12、 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 co
13、nstitute 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: Foreword - Supplementary information. T
14、he committee responsible for this document is ISO/IEC JTC 1, Information technology , SC 35, User interfaces. 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 descri
15、ption Part 4: Target description Part 5: Resource description Part 6: Web service integrationiv ISO/IEC 2014 All rights reserved ISO/IEC 24752-6:2014(E) Introduction Web services are becoming increasingly ubiquitous in the form of public Internet-wide services and private services in protected envir
16、onments. Even devices and appliances in the digital home are being made network-accessible by exposing them as Web services. The universal remote console technology allows for pluggable user interfaces for any kind of devices and services, including web services. For a web service to adopt the URC c
17、oncepts, it needs to expose a composition of user interface socket elements. This can be achieved in two ways: either the Web service provides one target description (see ISO/IEC 24752-4) or one or multiple separate user interface socket descriptions (see ISO/IEC 24752-2). Alternatively, the Web ser
18、vice can provide the target description and the socket description(s) in an “embedded” approach integrated with its Web service interface description. The web service description language (WSDL) defines suitable extension mechanisms for such integration. With this integrated approach, Web services d
19、o not need to provide a separate target description and separate socket descriptions. It is sufficient to integrate this information into their WSDL document. It is expected that this approach will help in the adoption of the URC technology for Web services and thus, make personalized and pluggable
20、user interfaces widely available for Web services. This part of ISO/IEC 24752 defines the syntax and semantics for embedding target description and socket descriptions in interface specifications of Web services so that there is a clear mapping between special elements in the WSDL document and eleme
21、nts of (implicit) target description and (implicit) socket descriptions. This part of ISO/IEC 24752 lays the groundwork for an integration of the universal remote console framework within Web service environments. It gives rise to various URC-based architectures and implementations, including a midd
22、leware approach in which a user interface server provides access to web services, and Web service centric approach in which a Web service exposes a user interface socket via its WSDL-based interface. ISO/IEC 2014 All rights reserved v Information technology User interfaces Universal remote console P
23、art 6: Web service integration 1 Scope This part of ISO/IEC 24752 defines the syntax and semantics for embedding target description and socket descriptions in interface specifications of web services so that there is a clear mapping between special elements in the WSDL document and elements of (impl
24、icit) target description and (implicit) socket descriptions. 2 Conformance A WSDL1 document conforms to this International Standard if it complies to the web services description language (WSDL) 1.1 specification and with the requirements and recommendations in Clause 6 and Clause 7. A WSDL2 documen
25、t conforms to this International Standard if it complies to the web services description language (WSDL) 2.0 specification and with the requirements and recommendations in Clause 6 and Clause 7. NOTE Strict language conformance (i.e. no additional elements or attributes allowed) is not required beca
26、use 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. A Web service conforms to this International Standard if it fulfils the requir
27、ements of a conforming target in ISO/IEC 24752-1, in all of the following ways. The Web service shall provide at least one service binding (as specified in the Web services WSDL document) as Target-URC network link. The Web service shall have a target name, given as the target namespace of the Web s
28、ervice, as specified in 7.5.2. The Web service shall have exactly one target description which shall be embedded in its WSDL document and shall include references to external files containing the target resources (grouping sheets and resource sheets) conforming to at least one natural language, as s
29、pecified in 7.5. The Web service shall provide a fetch mechanism for its target resources (grouping sheets, resource sheets, UIIDs) to be retrieved by URI, including support for MIME types. The Web service shall provide a target instance identifier through the getTargetInstanceId operation in the “_
30、target” partition, as specified in 7.5.11.2. The Web service shall support locator functions through a “_target” partition, as specified in 7.5.7. The Web service shall expose one or more sockets that, when considered together, cover the full functionality of the Web service as a target. For each of
31、 these sockets, a socket description shall be embedded in the Web services WSDL document (as specified in 7.6). For each of the Web services sockets, the socket shall have variables that include all of the dynamic data on the sockets state a user can perceive and/or manipulate and commands that incl
32、ude all of the sockets functions that can be called explicitly or implicitly by users and notifications that cover all exceptions that the Web service needs to inform the user about. INTERNATIONAL ST ANDARD ISO/IEC 24752-6:2014(E) ISO/IEC 2014 All rights reserved 1 ISO/IEC 24752-6:2014(E) The Web se
33、rvice shall provide one grouping resource for every socket through external grouping sheets. The Web service shall provide textual label resources through external resource sheets, in at least one natural language. The Web service shall provide dynamic atomic resources at runtime for those socket el
34、ements where no (static) atomic resources are available in the target resources, as specified in 7.6.21.5, 7.6.22.5, and 7.6.23.6. The Web service, if representing a session-full target, shall support an open session request from a URC, as specified in 7.6.15. The Web service, if representing a sess
35、ion-full target, shall support a close session event from a URC, as specified in 7.6.16. The Web service, if representing a session-full target, shall support a suspend session event from a URC, as specified in 7.6.17. The Web service, if representing a session-full target, shall support a resume se
36、ssion event from a URC, as specified in 7.6.18. The Web service, if representing a session-full target, shall send an abort session event in case of user session abortion, as specified in 7.6.14. The Web service shall track connection status information from the underlying network its operations are
37、 bound to. The Web service, if representing a session-full target, shall send a session forward event to the URC in case of session forwarding, as specified in 7.6.14. The Web service, if representing a session-full target, shall create and maintain a session between a socket and the URC after a suc
38、cessful open session request. The Web service shall indicate to the URC the availability of socket elements at runtime (unavailable socket elements have an undefined value). The Web service shall synchronize the socket variables between the socket and the URCs that participate in a joint session wit
39、h the socket (by means of the get-updates operation and the get operations of the variables). The Web service shall support command invocation requests from a URC (including handling of local parameters) and synchronization of command states (by means of the command operations). The Web service shal
40、l support propagation of notification states and, for custom-type notifications, embedded variables and commands, to the connected URCs, and acceptance of pertinent acknowledgments (by means of the get-updates operation and the check operations). The Web service shall synchronize actual indices of s
41、ocket sets and elements (by means of the get- index operations). The Web service shall not rely on the URC doing the interpretation of socket element dependencies. Provide the following mechanisms with regard to user response timeouts: a) after a timeout extension, return to the state of the task th
42、e user had reached prior to the timeout; b) support the extend-timeout operation (see 7.6.23.4) for notifications that time out and let the client extend the timeout at least to five times the default timeout; c) note time out notifications in less than 10 s.2 ISO/IEC 2014 All rights reserved ISO/IE
43、C 24752-6:2014(E) 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 (i
44、ncluding any amendments) applies. ISO/IEC 24752-1, Information technology User interfaces Universal remote console Part 1: Framework ISO/IEC 24752-2:2013, Information technology User interfaces Universal remote console Part 2: User interface socket description ISO/IEC 24752-4:2013, Information techn
45、ology User interfaces Universal remote console Part 4: Target description 4 T erms a nd definiti ons For the purposes of this document, the terms and definitions given in ISO/IEC 24752-1, ISO/IEC 24752-2 and ISO/IEC 24752-4 and the following apply: 4.1 fault item named fault entity of a Web service
46、operation, i.e. in WSDL1 a referenced from a element of an , and in WSDL2 an element of an referencing an interface fault 4.2 input item named entity of input for a Web service operation, i.e. in WSDL1 a of a referenced from an element of an ; and in WSDL2 an element of an 4.3 item element name XML
47、element name for an input or output item, i.e. in WSDL1 the value of the element attribute on the pertaining message; and in WSDL2 the value of the element attribute on the message 4.4 partition Web service partition named set of a Web service operations (“port type” in WSDL1, “interface” in WSDL2)
48、4.5 output item named entity of output from a Web service operation, i.e. in WSDL1 a of a referenced from an element of an , and in WSDL2 an element of an 4.6 session-full socket socket of a session-full target 4.7 session-less socket socket of a session-less target 4.8 WSDL1 document document that
49、conforms to the Web Service Description Language (WSDL) 1.1 specification 4.9 WSDL2 document document that conforms to the Web Service Description Language (WSDL) 2.0 specification ISO/IEC 2014 All rights reserved 3 ISO/IEC 24752-6:2014(E) 5 Relation to other standards 5.1 Relation to XML This specification builds upon the extensible Markup Language (XML). Markup in XML is case sensitive. Tag names, an
