Information technology - User interfaces - Universal remote console - Part 6: Web service integration
Introduction: Web services are becoming increasingly ubiquitous in the form of public Internet-wide services and private services in protected environments. 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 concepts, 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 service 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 do 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 user interfaces widely available for Web services. This part of ISO/IEC 24752 defines the syntax and semantics for embedding target description and socket description
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 (implicit) 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 document 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 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. A Web service conforms to this International Standard if it fulfils the requirements 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 service’s WSDL document) as Target-URC network link. — The Web service shall have a target name, given as the target namespace of the Web service, 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 specified 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 “_target” partition, as specified in 7.5.11.2. — The Web service shall support locator functions through a “_target” partition,