draft-ietf-widex-requirements-01.txt   draft-ietf-widex-requirements-02.txt 
WIDEX V. Stirbu WIDEX V. Stirbu
Internet-Draft Nokia Internet-Draft Nokia
Intended status: Informational D. Raggett Intended status: Informational D. Raggett
Expires: October 13, 2006 W3C/Volantis Expires: November 15, 2006 W3C/Volantis
April 11, 2006 May 14, 2006
Widget Description Exchange Service (WIDEX) Requirements Widget Description Exchange Service (WIDEX) Requirements
draft-ietf-widex-requirements-01 draft-ietf-widex-requirements-02
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 35 skipping to change at page 1, line 35
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on October 13, 2006. This Internet-Draft will expire on November 15, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The Internet Society (2006).
Abstract Abstract
This document defines functional requirements for a framework and a This document defines functional requirements for a framework and a
protocol used to support XML-based user interfaces, where the user protocol used to support XML-based user interfaces, where the user
interface and application logic may be on different machines, and interface and application logic may be on different machines, and
skipping to change at page 5, line 25 skipping to change at page 5, line 25
3.3. Widex Objects 3.3. Widex Objects
One of the goals of the Widex working group is to define Widex One of the goals of the Widex working group is to define Widex
Objects (WO), to be used to convey information about interface Objects (WO), to be used to convey information about interface
updates and events. WOs are used to keep the rendered user interface updates and events. WOs are used to keep the rendered user interface
synchronised with the application logic. synchronised with the application logic.
There are two types of WOs: There are two types of WOs:
WO Update (RUI.Update): WO Update (WO.Update):
WO.Update messages contain description of changes to XML DOM WO.Update messages contain description of changes to XML DOM
trees. The updates can target individual nodes in order to update trees. The updates can target individual nodes in order to update
their properties and attributes, or can target parts of the DOM their properties and attributes, or can target parts of the DOM
tree in order change its structure, e.g. add/delete/replace nodes tree in order change its structure, e.g. add/delete/replace nodes
or branches. or branches.
WO Event (WO.Event): WO Event (WO.Event):
WO.Event messages are primarily used to carry events triggered on WO.Event messages are primarily used to carry events triggered on
the Widex Renderer side so that they can be caught by the the Widex Renderer side so that they can be caught by the
application logic event handlers on the Widex Server side. Not application logic event handlers on the Widex Server side. Not
skipping to change at page 6, line 7 skipping to change at page 6, line 7
per Extensible Multi-Modal Annotations [EMMA], which uses XML for per Extensible Multi-Modal Annotations [EMMA], which uses XML for
annotated interpretations of user input. annotated interpretations of user input.
A secondary use of WO.Event messages is where the application A secondary use of WO.Event messages is where the application
logic itself raises events that may be caught by event handlers logic itself raises events that may be caught by event handlers
associated with the remote user interface, see for example Web associated with the remote user interface, see for example Web
Applications 1.0 [WhatWG.WebApps1.0]. Applications 1.0 [WhatWG.WebApps1.0].
3.4. Transport Protocol 3.4. Transport Protocol
The Transport Protocol is a protocol that just transports the RUIOs The Transport Protocol is a protocol that just transports the WOs as
as a string of bits, without looking at them. a string of bits, without looking at them.
3.5. Simple vs. Complex User Interfaces 3.5. Simple vs. Complex User Interfaces
Simple User Interface: Simple User Interface:
A simple user interface allows the user interface to be A simple user interface allows the user interface to be
represented with only one XML DOM object. represented with only one XML DOM object.
Complex User Interface: Complex User Interface:
A complex user interface may include scripted client-side event A complex user interface may include scripted client-side event
handlers or there can be more than one XML DOM in the user handlers or there can be more than one XML DOM in the user
interface, e.g. different DOMs for different modalities, but see interface, e.g. different DOMs for different modalities, but see
also SVG's XML Binding Language [sXBL] for the role of shadow also SVG's XML Binding Language [sXBL] for the role of shadow
DOMs. DOMs.
3.6. Session 3.6. Session
The Widex Session is initiated between a Widex Servers and a Widex The Widex Session is initiated between a Widex Server and a Widex
Renderer for exchanging information about user interface updates and Renderer for exchanging information about user interface updates and
events in order to control applications remotely. A Widex Session events in order to control applications remotely. A Widex Session
relate to a single User Interface, which can be simple or complex. relate to a single User Interface, which can be simple or complex.
4. Scenarios and Explanatory Discussion 4. Scenarios and Explanatory Discussion
In this section we introduce short scenarios to illustrate how Widex In this section we introduce short scenarios to illustrate how Widex
services can be deployed in some environments. services can be deployed in some environments.
4.1. NAT Traversal 4.1. NAT Traversal
skipping to change at page 8, line 32 skipping to change at page 8, line 32
The network might be managed in which case a centralised service The network might be managed in which case a centralised service
discovery and session setup mechanism should be used, or unmanaged discovery and session setup mechanism should be used, or unmanaged
and a peer-to-peer service discovery and session setup mechanism and a peer-to-peer service discovery and session setup mechanism
should be used. should be used.
4.2. IPv4-IPv6 Interworking 4.2. IPv4-IPv6 Interworking
The global deployment of IPv6 is underway, creating an IPv4/IPv6 The global deployment of IPv6 is underway, creating an IPv4/IPv6
Internet consisting of IPv4-only and dual-stack IPv4/IPv6 networks Internet consisting of IPv4-only and dual-stack IPv4/IPv6 networks
and nodes. There may also be IPv6-only nodes. It is highly probable and nodes RFC 4213 [RFC4213]. There may also be IPv6-only nodes. It
that there will be situations when IPv4-only Widex entities will want is highly probable that there will be situations when IPv4-only Widex
to communicate with dual-stack IPv4/IPv6 Widex entities. Also, a entities will want to communicate with dual-stack IPv4/IPv6 Widex
valid scenario is where two dual-stack IPv4/IPv6 Widex entities are entities. Also, a valid scenario is where two dual-stack IPv4/IPv6
communicating over a network that includes an IPv4-only segment. In Widex entities are communicating over a network that includes an
these scenarios, it is expected that at least one Widex Element will IPv4-only segment. In these scenarios, it is expected that at least
be attached to an unmanaged network or to a 3GPP network; IPv6 one Widex Element will be attached to an unmanaged network or to a
transition scenarios for unmanaged networks are described in RFC 3750 3GPP network; IPv6 transition scenarios for unmanaged networks are
[RFC3750] and for 3GPP networks are described in RFC 3574 [RFC3574]. described in RFC 3750 [RFC3750] and for 3GPP networks are described
in RFC 3574 [RFC3574].
A good guideline, when talking about migrating from IPv4 to IPv6, is A good guideline, when talking about migrating from IPv4 to IPv6, is
to select such protocols that do not have big issues with NAT to select such protocols that do not have big issues with NAT
traversal and IPv6 transition mechanisms. traversal and IPv6 transition mechanisms.
In the following sections, we will describe some of the common In the following sections, we will describe some of the common
scenarios involving Widex Elements and IPv4-IPv6 interworking. scenarios involving Widex Elements and IPv4-IPv6 interworking.
4.2.1. Dual-Stack Widex Element Communicating with IPv4-Only Widex 4.2.1. Dual-Stack Widex Element Communicating with IPv4-Only Widex
Element Using IPv4 Element Using IPv4
skipping to change at page 10, line 37 skipping to change at page 10, line 37
Architecture [MMI.Arch]. Architecture [MMI.Arch].
5.2. Discovery and Session Setup Requirements 5.2. Discovery and Session Setup Requirements
o The service discovery mechanism MUST be able to discover both o The service discovery mechanism MUST be able to discover both
Widex Renderers and Widex Servers. Widex Renderers and Widex Servers.
o The service discovery mechanism MUST be able to negotiate the o The service discovery mechanism MUST be able to negotiate the
capabilities of both Widex Renderers and Widex Servers, e.g. capabilities of both Widex Renderers and Widex Servers, e.g.
supported devices physical characteristics, supported markup supported devices physical characteristics, supported markup
languages, etc. languages, etc.
o The session setup mechanism MUST be able to establish sessions o The session setup mechanism MUST be able to initiate session
from both Widex Renderers and Widex Servers, e.g. remote user establishment from both Widex Renderers and Widex Servers, e.g.
interface pull and push. remote user interface pull and push.
5.3. Widex Objects Requirements 5.3. Widex Objects Requirements
o The WOs MUST NOT be aware of the semantics of the markup that is o The WOs MUST NOT be aware of the semantics of the UI markup
synchronized. language that is synchronized.
o The WOs MUST support client initiated updates. o The WOs MUST support client initiated updates.
o The WOs MUST support server initiated updates. o The WOs MUST support server initiated updates.
o The WOs MUST contain only information having remote scope. o The WOs MUST contain only information having remote scope.
o The WOs MUST indicate the target XML DOM tree when Complex User o The WOs MUST indicate the target XML DOM tree when Complex User
Interfaces are involved. Interfaces are involved.
o The WOs MAY support multiple modes of interaction, and it is the o The WOs MAY support multiple modes of interaction, and it is the
responsibility of the application to synchronise modalities and responsibility of the application to synchronise modalities and
not that of the Widex protocol. not that of the Widex protocol.
 End of changes. 9 change blocks. 
22 lines changed or deleted 23 lines changed or added

This html diff was produced by rfcdiff 1.31. The latest version is available from http://www.levkowetz.com/ietf/tools/rfcdiff/