Device coordination scope

From UWA
Jump to: navigation, search

The scope of Device Coordination

Device coordination considers resource description, discovery and binding, communications between devices, delivery context client interfaces, temporary and persistent sessions, etc. Then, the most of related considering points was already started in W3C

  • Resource Descriptions: In order to discover resources and recognize their usage and device capabilities, it is necessary to describe resources. Devices and services can be identified by URIs. RDF provides the basis for such descriptions, while OWL provides a means to express ontology for the properties and relationships used in these descriptions.
  • Discovery and Binding: Discovery and binding is the process of describing users’ needs and searching for a matching resource in order to provide services adapted to delivery context and/or user intents.
  • Communication between Devices: In order to provide the user with adapted services, communication among devices is important. It may be possible to interact between devices by targeting an event at a DOM node expressing the device. For example, if web application wants to adjust the printer configuration it can do so by sending an event to a DOM node representing the printer.
  • Delivery Context Client Interfaces: DCCI is the interfaces that provide the information related to user preference, device capabilities, and environmental condition for detecting delivery context and/or user intents. DCCI is extended from the document object model, and such resources are exposed as objects in the DOM. The DOM object can act as proxies for adjusting the resources.
  • Temporary and Persistent Sessions: Sessions may be temporary, for example, only lasting for the lifetime of a Web page, or permanent, such as for meeting rooms, which applications can join and leave. Sessions are resources in their own right and identified by a URI.