From remoteui-bounces@lists.ietf.org Thu Sep 01 06:08:41 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EAlzt-0007vo-RW; Thu, 01 Sep 2005 06:08:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EAlzs-0007vd-B2
	for remoteui@megatron.ietf.org; Thu, 01 Sep 2005 06:08:40 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10463
	for <remoteui@ietf.org>; Thu, 1 Sep 2005 06:08:38 -0400 (EDT)
Received: from homer.w3.org ([128.30.52.30])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EAm1m-0008Bi-S1
	for remoteui@ietf.org; Thu, 01 Sep 2005 06:10:40 -0400
Received: from localhost (homer.w3.org [128.30.52.30])
	by homer.w3.org (Postfix) with ESMTP id E3AEC4EEC4;
	Thu,  1 Sep 2005 06:08:36 -0400 (EDT)
Date: Thu, 1 Sep 2005 11:09:32 +0100 (BST)
From: Dave Raggett <dsr@w3.org>
X-X-Sender: dsr@holly
To: Vlad.Stirbu@nokia.com
Subject: Re: [REMOTEUI] Widex charter proposal draft
In-Reply-To: <1C1F3D15859526459B4DD0A7A9B2268BA0E7BF@trebe101.NOE.Nokia.com>
Message-ID: <Pine.LNX.4.61.0509010949420.10053@holly>
References: <1C1F3D15859526459B4DD0A7A9B2268BA0E7BF@trebe101.NOE.Nokia.com>
X-GPG-PUBLIC_KEY: http://www.w3.org/People/Raggett/pubkey-20040130.asc
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2beba50d0fcdeee5f091c59f204d4365
Cc: remoteui@ietf.org
X-BeenThere: remoteui@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Remote UI BoF and future WG discussion list <remoteui.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/remoteui>,
	<mailto:remoteui-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/remoteui>
List-Post: <mailto:remoteui@lists.ietf.org>
List-Help: <mailto:remoteui-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/remoteui>,
	<mailto:remoteui-request@lists.ietf.org?subject=subscribe>
Sender: remoteui-bounces@lists.ietf.org
Errors-To: remoteui-bounces@lists.ietf.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

This is a good start, but I agree with Eric about the first few
paragraphs and consider the protocol as being of broader use than 
the GUI widget scenario you describe. The terminology being used in 
the W3C Multimodal Interaction Working Group is that of "Modality 
Components" which provide a means to interact with users via one or 
more modalities, and which vary from simple to complex (e.g. an 
XHTML or VoiceXML web page). This is described in: 
http://www.w3.org/TR/mmi-arch/

How about the following:

With the Internet reaching out to more and more devices, people are 
increasingly expecting to have access to services at anytime, from 
anywhere and using any device. Such services are being developed 
using Web technologies such as XML and distributed across the 
network rather than resident on any one device.

An example is a service to access flight arrival times, where the 
user interface is expressed in XHTML and the application logic runs 
on a remote server. In this case, synchronization takes place in 
terms of a request/response protocol (HTTP) for Web pages. What
is currently lacking is a convenient means for finer grained 
synchronization that occurs in between page loads. This would allow 
the user interface to reflect changes in application state and offer 
greater flexibility for applications to respond to user input 
events.

This Working Group seeks to define a light weight synchronization
protocol for distributed user interfaces where the user interface
is represented in XML, and synchronization involves DOM events
and DOM mutation/update operations.


On Thu, 25 Aug 2005 Vlad.Stirbu@nokia.com wrote:

> Hi,
>
> Please find below the charter proposal for the WiDeX WG.
>
> Regards,
> Vlad
>
> ----------------------------------------------------------------
>
> Description of Working Group
>
> UI remoting is a technique whereby a user interface is rendered
> on other devices than those that run the application logic.
>
> A widget is an element of a user interface (UI) that displays 
> information or provides a specific way for a user to interact with 
> the operating system and application. Widgets may for instance 
> include icons, pull-down menus, buttons, selection boxes, progress 
> indicators, on-off checkmarks, scroll bars, windows, window edges 
> (that let you resize the window), toggle buttons, forms, and many 
> other devices for displaying information and for inviting, 
> accepting, and responding to user actions.
>
> Widget-level UI remoting provides a mechanism that enables a 
> client device to process widget descriptions received from a 
> server device, keeping the client UI synchronized with the 
> application logic.
>
> The WiDeX (Widget Description Exchange Service) WG will define a 
> standard mechanism that can be used in an IP-based network for 
> conveing initialization, update and eventing information about 
> user visible objects, i.e. widgets.
>
> The WG will strive to preserve an extensible architecture so that 
> the work possibly be useful in the future with other types of 
> descriptive user interfaces beyond those specifically considered 
> by the group.
>
> Specific topics that are NOT goals of this WG are:
>
>  - XML representation of user interface objects.
>  - Means to establish sessions and support for device 
>    coordination.
>
> The WiDeX service definition will define:
>
> - A mechanism for synchronizing distributed XML DOM objects by 
>   propagating DOM mutations/updates and DOM events.
> - A set of parameters that need to be negotiated by a service 
>   discovery and session setup mechanism in order to start the UI 
>   remoting session.
> - A framework that enables a widget-level UI remoting 
>   mechanism using distributed XML DOM synchronization and a 
>   service discovery and session setup mechanism as building 
>   blocks.
>
> Deliverables:
>
>  - Requirements document.
>  - Document specifying the stateless protocol for synchronizing 
>    XML DOM objects.
>  - Document specifying the framework for widget-level UI 
>    remoting.
>
> It is possible that work undertaken in other working groups and 
> even other standards bodies (i.e. W3C) will be referenced by this 
> working group. It is even possible that entire deliverables could 
> be satisfied by the work of other working groups (i.e. discovery 
> protocols). This working group will seek to maximize the use of 
> existing specifications where applicable.
>
> Goals and Milestones:
>
> TBD.
>
> Internet-Drafts:
>
> LRDP: The Lightweight Remote Display Protocol, 
> http://www.ietf.org/internet-drafts/draft-stirbu-lrdp-00.txt
>

- --
  Dave Raggett <dsr@w3.org>  W3C lead for multimodal interaction
  http://www.w3.org/People/Raggett +44 1225 866240 (or 867351)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFDFtNgb3AdEmxAsUsRAtUOAKClD4VYHnQUMIt0fQBQYWsq2C7aWwCg/dR1
+4KszCMQHOzEVDX6kkqgUbE=
=H+ZO
-----END PGP SIGNATURE-----

_______________________________________________
REMOTEUI mailing list
REMOTEUI@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/remoteui



From remoteui-bounces@lists.ietf.org Thu Sep 01 10:41:21 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EAqFl-0007SB-Dw; Thu, 01 Sep 2005 10:41:21 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EAqFj-0007S2-0X
	for remoteui@megatron.ietf.org; Thu, 01 Sep 2005 10:41:19 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08505
	for <remoteui@ietf.org>; Thu, 1 Sep 2005 10:41:16 -0400 (EDT)
Received: from homer.w3.org ([128.30.52.30])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EAqHf-0000YC-MU
	for remoteui@ietf.org; Thu, 01 Sep 2005 10:43:20 -0400
Received: from localhost (homer.w3.org [128.30.52.30])
	by homer.w3.org (Postfix) with ESMTP id 882444EEB3;
	Thu,  1 Sep 2005 10:41:15 -0400 (EDT)
Date: Thu, 1 Sep 2005 15:42:10 +0100 (BST)
From: Dave Raggett <dsr@w3.org>
X-X-Sender: dsr@holly
To: Vlad.Stirbu@nokia.com
Subject: Re: [REMOTEUI] Widex charter proposal draft
In-Reply-To: <Pine.LNX.4.61.0509010949420.10053@holly>
Message-ID: <Pine.LNX.4.61.0509011438420.10053@holly>
References: <1C1F3D15859526459B4DD0A7A9B2268BA0E7BF@trebe101.NOE.Nokia.com>
	<Pine.LNX.4.61.0509010949420.10053@holly>
X-GPG-PUBLIC_KEY: http://www.w3.org/People/Raggett/pubkey-20040130.asc
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Cc: remoteui@ietf.org
X-BeenThere: remoteui@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Remote UI BoF and future WG discussion list <remoteui.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/remoteui>,
	<mailto:remoteui-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/remoteui>
List-Post: <mailto:remoteui@lists.ietf.org>
List-Help: <mailto:remoteui-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/remoteui>,
	<mailto:remoteui-request@lists.ietf.org?subject=subscribe>
Sender: remoteui-bounces@lists.ietf.org
Errors-To: remoteui-bounces@lists.ietf.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Some further questions.

To make the protocol more concrete we might want to bind it to
SIP and to mention this in the charter.

SIP is an obvious choice because of its use for establishing
sessions and for distributing events (represented in XML),
although the focus has hitherto been on presence information.
SIP is also widely deployed on desktop and mobile devices.
Web Services and the widespread deployment of HTTP make the
latter another candidate worthy of discussion.

We could also use the charter to constrain the work by mentioning
technical assumptions. Here are two that I have thought of:

First, when an event is raised in the user interface, the DOM is 
responsible for passing it to event handlers according to the
DOM event capture/bubble model. If an event is passed to a remote 
handler, the User interface should be able to pass the event to
the next handler without having to worry about whether or not the
remote handler calls the stopPropagation method. A similar concern
relates to the preventDefault method. I therefore suggest that
these two methods have no effect when called by a remote handler
of a DOM event. This ensure that events can be asynchronously
passed off to remote handlers.

Second, if the user interface wants to modify the document, it
is required to pass the request as an event to the document owner
which is then responsible for making the corresponding changes.
Note that the user interface may involve more than one document
and that these may have different owners. Moreover, this only
applies to documents that are under synchronization. Other
documents may be freely updated by default event handlers or
local scripts.

We may also want to constrain what we intend for the framework
for session initiation. For instance, in:

   http://whatwg.org/specs/web-apps/current-work/#server-sent

section 6.1.2 defines an extension to the DOM for a 
RemoteEventTarget interface that should be supported by any
object that implements the DOM EventTarget interface. The idea
is to use URIs to specify the means to subscribe to an event
or list of events and correspondingly to unsubscribe:

    // src is used for a URI in both cases
    interface RemoteEventTarget {
       void addEventSource(in DOMString src);
       void removeEventSource(in DOMString src);
    };

This is fine for sourcing events from a remote device, but 
inadequate for our purposes where the UI device needs to
send selected events to a sink on the application server,
and to receive DOM mutation/update operations from that
server. Is this information expressed in the UI markup and
acted upon by the markup language interpreter, or is it set
up via an out of band mechanism such as the SIP/SDP etc.
where the information is passed separately to the markup.

- -- 
  Dave Raggett <dsr@w3.org>  W3C lead for multimodal interaction
  http://www.w3.org/People/Raggett +44 1225 866240 (or 867351)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFDFxNIb3AdEmxAsUsRAmelAJ9B9BHwRNY/G42HoRcYzk7LWa26fQCgrabi
daEL4h0/Myo+4Us6Ct4WbSw=
=2qaf
-----END PGP SIGNATURE-----

_______________________________________________
REMOTEUI mailing list
REMOTEUI@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/remoteui



From remoteui-bounces@lists.ietf.org Thu Sep 01 22:06:52 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EB0x9-0002Ci-T1; Thu, 01 Sep 2005 22:06:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EB0x7-0002CF-Pe
	for remoteui@megatron.ietf.org; Thu, 01 Sep 2005 22:06:50 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13779
	for <remoteui@ietf.org>; Thu, 1 Sep 2005 22:06:47 -0400 (EDT)
Received: from salvelinus.brooktrout.com ([204.176.205.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EB0zA-00054K-L3
	for remoteui@ietf.org; Thu, 01 Sep 2005 22:08:57 -0400
Received: from ATLANTIS.Brooktrout.com (oceans11.brooktrout.com
	[204.176.75.121])
	by salvelinus.brooktrout.com (8.12.5/8.12.5) with ESMTP id
	j82222tZ011055; Thu, 1 Sep 2005 22:02:02 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [REMOTEUI] Widex charter proposal draft
Date: Thu, 1 Sep 2005 22:01:58 -0400
Message-ID: <330A23D8336C0346B5C1A5BB19666647F55102@ATLANTIS.Brooktrout.com>
Thread-Topic: [REMOTEUI] Widex charter proposal draft
Thread-Index: AcWvA0PP5Yj8iR1tRae2hGs5mwvjaAAXsn9A
From: "Eric Burger" <eburger@brooktrout.com>
To: "Dave Raggett" <dsr@w3.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Content-Transfer-Encoding: quoted-printable
Cc: remoteui@ietf.org
X-BeenThere: remoteui@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Remote UI BoF and future WG discussion list <remoteui.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/remoteui>,
	<mailto:remoteui-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/remoteui>
List-Post: <mailto:remoteui@lists.ietf.org>
List-Help: <mailto:remoteui-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/remoteui>,
	<mailto:remoteui-request@lists.ietf.org?subject=subscribe>
Sender: remoteui-bounces@lists.ietf.org
Errors-To: remoteui-bounces@lists.ietf.org

I would agree on limiting the protocol to SIP, but we should have a
draft explaining why.  Namely, it is because the updates are
bi-directional.  If they were uni-directional, HTTP would probably do.

I would volunteer, but I have to finish my thesis first, and that
wouldn't make it as a chapter :)

-----Original Message-----
From: remoteui-bounces@lists.ietf.org
[mailto:remoteui-bounces@lists.ietf.org] On Behalf Of Dave Raggett
Sent: Thursday, September 01, 2005 10:42 AM
To: Vlad.Stirbu@nokia.com
Cc: remoteui@ietf.org
Subject: Re: [REMOTEUI] Widex charter proposal draft

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Some further questions.

To make the protocol more concrete we might want to bind it to
SIP and to mention this in the charter.

SIP is an obvious choice because of its use for establishing
sessions and for distributing events (represented in XML),
although the focus has hitherto been on presence information.
SIP is also widely deployed on desktop and mobile devices.
Web Services and the widespread deployment of HTTP make the
latter another candidate worthy of discussion.

We could also use the charter to constrain the work by mentioning
technical assumptions. Here are two that I have thought of:

First, when an event is raised in the user interface, the DOM is=20
responsible for passing it to event handlers according to the
DOM event capture/bubble model. If an event is passed to a remote=20
handler, the User interface should be able to pass the event to
the next handler without having to worry about whether or not the
remote handler calls the stopPropagation method. A similar concern
relates to the preventDefault method. I therefore suggest that
these two methods have no effect when called by a remote handler
of a DOM event. This ensure that events can be asynchronously
passed off to remote handlers.

Second, if the user interface wants to modify the document, it
is required to pass the request as an event to the document owner
which is then responsible for making the corresponding changes.
Note that the user interface may involve more than one document
and that these may have different owners. Moreover, this only
applies to documents that are under synchronization. Other
documents may be freely updated by default event handlers or
local scripts.

We may also want to constrain what we intend for the framework
for session initiation. For instance, in:

   http://whatwg.org/specs/web-apps/current-work/#server-sent

section 6.1.2 defines an extension to the DOM for a=20
RemoteEventTarget interface that should be supported by any
object that implements the DOM EventTarget interface. The idea
is to use URIs to specify the means to subscribe to an event
or list of events and correspondingly to unsubscribe:

    // src is used for a URI in both cases
    interface RemoteEventTarget {
       void addEventSource(in DOMString src);
       void removeEventSource(in DOMString src);
    };

This is fine for sourcing events from a remote device, but=20
inadequate for our purposes where the UI device needs to
send selected events to a sink on the application server,
and to receive DOM mutation/update operations from that
server. Is this information expressed in the UI markup and
acted upon by the markup language interpreter, or is it set
up via an out of band mechanism such as the SIP/SDP etc.
where the information is passed separately to the markup.

- --=20
  Dave Raggett <dsr@w3.org>  W3C lead for multimodal interaction
  http://www.w3.org/People/Raggett +44 1225 866240 (or 867351)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFDFxNIb3AdEmxAsUsRAmelAJ9B9BHwRNY/G42HoRcYzk7LWa26fQCgrabi
daEL4h0/Myo+4Us6Ct4WbSw=3D
=3D2qaf
-----END PGP SIGNATURE-----

_______________________________________________
REMOTEUI mailing list
REMOTEUI@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/remoteui

_______________________________________________
REMOTEUI mailing list
REMOTEUI@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/remoteui



From remoteui-bounces@lists.ietf.org Fri Sep 02 02:22:57 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EB4wz-0006FL-MD; Fri, 02 Sep 2005 02:22:57 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EB4wx-0006FA-VG
	for remoteui@megatron.ietf.org; Fri, 02 Sep 2005 02:22:56 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA16794
	for <remoteui@ietf.org>; Fri, 2 Sep 2005 02:22:55 -0400 (EDT)
From: Vlad.Stirbu@nokia.com
Received: from mgw-ext04.nokia.com ([131.228.20.96])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EB4z4-0004Tk-29
	for remoteui@ietf.org; Fri, 02 Sep 2005 02:25:06 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext04.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id
	j826LhrQ016071; Fri, 2 Sep 2005 09:21:44 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 2 Sep 2005 09:22:50 +0300
Received: from trebe101.NOE.Nokia.com ([172.22.124.61]) by
	esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 2 Sep 2005 09:22:25 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [REMOTEUI] Widex charter proposal draft
Date: Fri, 2 Sep 2005 09:22:24 +0300
Message-ID: <1C1F3D15859526459B4DD0A7A9B2268BA0E7EA@trebe101.NOE.Nokia.com>
Thread-Topic: [REMOTEUI] Widex charter proposal draft
Thread-Index: AcWvA0PP5Yj8iR1tRae2hGs5mwvjaAAXsn9AAAgZ4aA=
To: <eburger@brooktrout.com>, <dsr@w3.org>, <remoteui@ietf.org>
X-OriginalArrivalTime: 02 Sep 2005 06:22:25.0374 (UTC)
	FILETIME=[AF6FB7E0:01C5AF86]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 8fbbaa16f9fd29df280814cb95ae2290
Content-Transfer-Encoding: quoted-printable
Cc: 
X-BeenThere: remoteui@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Remote UI BoF and future WG discussion list <remoteui.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/remoteui>,
	<mailto:remoteui-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/remoteui>
List-Post: <mailto:remoteui@lists.ietf.org>
List-Help: <mailto:remoteui-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/remoteui>,
	<mailto:remoteui-request@lists.ietf.org?subject=subscribe>
Sender: remoteui-bounces@lists.ietf.org
Errors-To: remoteui-bounces@lists.ietf.org

I'll have to disagree on this issue. One of the ideas behind the RUI BoF =
was that the protocol must be service discovery and session setup =
independent; there was a debate on what this "independent" really means =
and the answer was that the protocol should be usable with any existing =
service discover and session mechanism, e.g. SIP/SDP, UPnP, =
Rendezvous/Bonjour, etc., and that the protocol should not depend on a =
particular one. The reason behind this assumption/requirement is that we =
should be able to use the protocol in multiple environments regardless =
of what is the session setup mechanism in a particular one. For example, =
in a cellular network SIP/SDP is the right choice but in a home network =
(see www.dlna.org) where UPnP is used for service discovery we'll have =
to use UPnP Remote UI to start the ui remoting session.

In order to accommodate this situation and because it is clear that the =
service discovery and session setup mechanisms needs to negotiate =
something, the working group should provide the needed parameters to =
facilitate session setup but we should not include these service =
discovery and session setup mechanisms in the charter.

Vlad

> -----Original Message-----
> From: remoteui-bounces@lists.ietf.org
> [mailto:remoteui-bounces@lists.ietf.org]On Behalf Of ext Eric Burger
> Sent: 02 September, 2005 05:02
> To: Dave Raggett
> Cc: remoteui@ietf.org
> Subject: RE: [REMOTEUI] Widex charter proposal draft
>=20
>=20
> I would agree on limiting the protocol to SIP, but we should have a
> draft explaining why.  Namely, it is because the updates are
> bi-directional.  If they were uni-directional, HTTP would probably do.
>=20
> I would volunteer, but I have to finish my thesis first, and that
> wouldn't make it as a chapter :)
>=20
> -----Original Message-----
> From: remoteui-bounces@lists.ietf.org
> [mailto:remoteui-bounces@lists.ietf.org] On Behalf Of Dave Raggett
> Sent: Thursday, September 01, 2005 10:42 AM
> To: Vlad.Stirbu@nokia.com
> Cc: remoteui@ietf.org
> Subject: Re: [REMOTEUI] Widex charter proposal draft
>=20
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> Some further questions.
>=20
> To make the protocol more concrete we might want to bind it to
> SIP and to mention this in the charter.
>=20
> SIP is an obvious choice because of its use for establishing
> sessions and for distributing events (represented in XML),
> although the focus has hitherto been on presence information.
> SIP is also widely deployed on desktop and mobile devices.
> Web Services and the widespread deployment of HTTP make the
> latter another candidate worthy of discussion.
>=20
> We could also use the charter to constrain the work by mentioning
> technical assumptions. Here are two that I have thought of:
>=20
> First, when an event is raised in the user interface, the DOM is=20
> responsible for passing it to event handlers according to the
> DOM event capture/bubble model. If an event is passed to a remote=20
> handler, the User interface should be able to pass the event to
> the next handler without having to worry about whether or not the
> remote handler calls the stopPropagation method. A similar concern
> relates to the preventDefault method. I therefore suggest that
> these two methods have no effect when called by a remote handler
> of a DOM event. This ensure that events can be asynchronously
> passed off to remote handlers.
>=20
> Second, if the user interface wants to modify the document, it
> is required to pass the request as an event to the document owner
> which is then responsible for making the corresponding changes.
> Note that the user interface may involve more than one document
> and that these may have different owners. Moreover, this only
> applies to documents that are under synchronization. Other
> documents may be freely updated by default event handlers or
> local scripts.
>=20
> We may also want to constrain what we intend for the framework
> for session initiation. For instance, in:
>=20
>    http://whatwg.org/specs/web-apps/current-work/#server-sent
>=20
> section 6.1.2 defines an extension to the DOM for a=20
> RemoteEventTarget interface that should be supported by any
> object that implements the DOM EventTarget interface. The idea
> is to use URIs to specify the means to subscribe to an event
> or list of events and correspondingly to unsubscribe:
>=20
>     // src is used for a URI in both cases
>     interface RemoteEventTarget {
>        void addEventSource(in DOMString src);
>        void removeEventSource(in DOMString src);
>     };
>=20
> This is fine for sourcing events from a remote device, but=20
> inadequate for our purposes where the UI device needs to
> send selected events to a sink on the application server,
> and to receive DOM mutation/update operations from that
> server. Is this information expressed in the UI markup and
> acted upon by the markup language interpreter, or is it set
> up via an out of band mechanism such as the SIP/SDP etc.
> where the information is passed separately to the markup.
>=20
> - --=20
>   Dave Raggett <dsr@w3.org>  W3C lead for multimodal interaction
>   http://www.w3.org/People/Raggett +44 1225 866240 (or 867351)
>=20
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (GNU/Linux)
>=20
> iD8DBQFDFxNIb3AdEmxAsUsRAmelAJ9B9BHwRNY/G42HoRcYzk7LWa26fQCgrabi
> daEL4h0/Myo+4Us6Ct4WbSw=3D
> =3D2qaf
> -----END PGP SIGNATURE-----
>=20
> _______________________________________________
> REMOTEUI mailing list
> REMOTEUI@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/remoteui
>=20
> _______________________________________________
> REMOTEUI mailing list
> REMOTEUI@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/remoteui
>=20

_______________________________________________
REMOTEUI mailing list
REMOTEUI@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/remoteui



From remoteui-bounces@lists.ietf.org Fri Sep 02 03:58:11 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EB6R9-0004sv-Gx; Fri, 02 Sep 2005 03:58:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EB6R6-0004sq-Ok
	for remoteui@megatron.ietf.org; Fri, 02 Sep 2005 03:58:09 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA21197
	for <remoteui@ietf.org>; Fri, 2 Sep 2005 03:58:07 -0400 (EDT)
Received: from homer.w3.org ([128.30.52.30])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EB6TC-0007jB-1v
	for remoteui@ietf.org; Fri, 02 Sep 2005 04:00:20 -0400
Received: from localhost (homer.w3.org [128.30.52.30])
	by homer.w3.org (Postfix) with ESMTP id CD0194EEC7;
	Fri,  2 Sep 2005 03:58:04 -0400 (EDT)
Date: Fri, 2 Sep 2005 08:59:02 +0100 (BST)
From: Dave Raggett <dsr@w3.org>
X-X-Sender: dsr@holly
To: Vlad.Stirbu@nokia.com
Subject: RE: [REMOTEUI] Widex charter proposal draft
In-Reply-To: <1C1F3D15859526459B4DD0A7A9B2268BA0E7EA@trebe101.NOE.Nokia.com>
Message-ID: <Pine.LNX.4.61.0509020845190.10101@holly>
References: <1C1F3D15859526459B4DD0A7A9B2268BA0E7EA@trebe101.NOE.Nokia.com>
X-GPG-PUBLIC_KEY: http://www.w3.org/People/Raggett/pubkey-20040130.asc
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Cc: remoteui@ietf.org
X-BeenThere: remoteui@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Remote UI BoF and future WG discussion list <remoteui.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/remoteui>,
	<mailto:remoteui-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/remoteui>
List-Post: <mailto:remoteui@lists.ietf.org>
List-Help: <mailto:remoteui-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/remoteui>,
	<mailto:remoteui-request@lists.ietf.org?subject=subscribe>
Sender: remoteui-bounces@lists.ietf.org
Errors-To: remoteui-bounces@lists.ietf.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, 2 Sep 2005 Vlad.Stirbu@nokia.com wrote:

> One of the ideas behind the RUI BoF was that the protocol must be 
> service discovery and session setup independent; there was a 
> debate on what this "independent" really means and the answer was 
> that the protocol should be usable with any existing service 
> discover and session mechanism, e.g. SIP/SDP, UPnP, 
> Rendezvous/Bonjour, etc., and that the protocol should not depend 
> on a particular one.

Sorry for not having made myself clearer. I believe we all agree on 
defining the message formats for DOM events and updates using XML in 
a way that is independent of the transport protocol. However, I feel 
it would be valuable to also provide a normative binding to at least 
one transport protocol such as SIP so that people can implement the 
solution in an interoperable way.

> The reason behind this assumption/requirement is that we should be 
> able to use the protocol in multiple environments regardless of 
> what is the session setup mechanism in a particular one. For 
> example, in a cellular network SIP/SDP is the right choice but in 
> a home network (see www.dlna.org) where UPnP is used for service 
> discovery we'll have to use UPnP Remote UI to start the ui 
> remoting session.

Which event transport protocol would you use in a home network,
and why couldn't we include bindings to that in the spec?

Providing explicit bindings makes the proposal much more concrete
and will attract more implementers.

- -- 
  Dave Raggett <dsr@w3.org>  W3C lead for multimodal interaction
  http://www.w3.org/People/Raggett +44 1225 866240 (or 867351)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFDGAZLb3AdEmxAsUsRAsnLAKCzaKVga5YPY9v799a+8GZP1/F9WwCg3jjq
+Y9zEg7i+EdiRAtZ+F3LYCs=
=fwDq
-----END PGP SIGNATURE-----

_______________________________________________
REMOTEUI mailing list
REMOTEUI@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/remoteui



From remoteui-bounces@lists.ietf.org Fri Sep 02 04:18:58 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EB6lG-0005nh-5f; Fri, 02 Sep 2005 04:18:58 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EB6lD-0005nZ-Nj
	for remoteui@megatron.ietf.org; Fri, 02 Sep 2005 04:18:56 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22360
	for <remoteui@ietf.org>; Fri, 2 Sep 2005 04:18:54 -0400 (EDT)
From: Vlad.Stirbu@nokia.com
Received: from mgw-ext04.nokia.com ([131.228.20.96])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EB6nK-0000EL-VU
	for remoteui@ietf.org; Fri, 02 Sep 2005 04:21:07 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext04.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id
	j828Hcis000638; Fri, 2 Sep 2005 11:17:40 +0300
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 2 Sep 2005 11:18:47 +0300
Received: from trebe101.NOE.Nokia.com ([172.22.124.61]) by
	esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 2 Sep 2005 11:18:46 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [REMOTEUI] Widex charter proposal draft
Date: Fri, 2 Sep 2005 11:18:45 +0300
Message-ID: <1C1F3D15859526459B4DD0A7A9B2268BA0E7F0@trebe101.NOE.Nokia.com>
Thread-Topic: [REMOTEUI] Widex charter proposal draft
Thread-Index: AcWvlBfdqDvKG8clSeyDLAx3VGKnhQAADwSA
To: <dsr@w3.org>
X-OriginalArrivalTime: 02 Sep 2005 08:18:46.0125 (UTC)
	FILETIME=[F049C9D0:01C5AF96]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Content-Transfer-Encoding: quoted-printable
Cc: remoteui@ietf.org
X-BeenThere: remoteui@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Remote UI BoF and future WG discussion list <remoteui.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/remoteui>,
	<mailto:remoteui-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/remoteui>
List-Post: <mailto:remoteui@lists.ietf.org>
List-Help: <mailto:remoteui-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/remoteui>,
	<mailto:remoteui-request@lists.ietf.org?subject=subscribe>
Sender: remoteui-bounces@lists.ietf.org
Errors-To: remoteui-bounces@lists.ietf.org

Well, I think that we agreed to have the protocol UI semantic =
independent and discovery and session setup mechanism independent. We =
haven't mentioned that the protocol should be transport protocol =
independent.

In fact, the whole purpose of the working group is to define a single =
mandatory to implement protocol for synchronising XML DOM events.

Vlad

> -----Original Message-----
> From: ext Dave Raggett [mailto:dsr@w3.org]
> Sent: 02 September, 2005 10:59
> To: Stirbu Vlad (Nokia-TP-MSW/Tampere)
> Cc: eburger@brooktrout.com; remoteui@ietf.org
> Subject: RE: [REMOTEUI] Widex charter proposal draft
>=20
>=20
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> On Fri, 2 Sep 2005 Vlad.Stirbu@nokia.com wrote:
>=20
> > One of the ideas behind the RUI BoF was that the protocol must be=20
> > service discovery and session setup independent; there was a=20
> > debate on what this "independent" really means and the answer was=20
> > that the protocol should be usable with any existing service=20
> > discover and session mechanism, e.g. SIP/SDP, UPnP,=20
> > Rendezvous/Bonjour, etc., and that the protocol should not depend=20
> > on a particular one.
>=20
> Sorry for not having made myself clearer. I believe we all agree on=20
> defining the message formats for DOM events and updates using XML in=20
> a way that is independent of the transport protocol. However, I feel=20
> it would be valuable to also provide a normative binding to at least=20
> one transport protocol such as SIP so that people can implement the=20
> solution in an interoperable way.
>=20
> > The reason behind this assumption/requirement is that we should be=20
> > able to use the protocol in multiple environments regardless of=20
> > what is the session setup mechanism in a particular one. For=20
> > example, in a cellular network SIP/SDP is the right choice but in=20
> > a home network (see www.dlna.org) where UPnP is used for service=20
> > discovery we'll have to use UPnP Remote UI to start the ui=20
> > remoting session.
>=20
> Which event transport protocol would you use in a home network,
> and why couldn't we include bindings to that in the spec?
>=20
> Providing explicit bindings makes the proposal much more concrete
> and will attract more implementers.
>=20
> - --=20
>   Dave Raggett <dsr@w3.org>  W3C lead for multimodal interaction
>   http://www.w3.org/People/Raggett +44 1225 866240 (or 867351)
>=20
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (GNU/Linux)
>=20
> iD8DBQFDGAZLb3AdEmxAsUsRAsnLAKCzaKVga5YPY9v799a+8GZP1/F9WwCg3jjq
> +Y9zEg7i+EdiRAtZ+F3LYCs=3D
> =3DfwDq
> -----END PGP SIGNATURE-----
>=20

_______________________________________________
REMOTEUI mailing list
REMOTEUI@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/remoteui



From remoteui-bounces@lists.ietf.org Fri Sep 02 04:55:53 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EB7Kz-00063j-90; Fri, 02 Sep 2005 04:55:53 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EB7Kw-00060a-Kd
	for remoteui@megatron.ietf.org; Fri, 02 Sep 2005 04:55:51 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA24203
	for <remoteui@ietf.org>; Fri, 2 Sep 2005 04:55:49 -0400 (EDT)
Received: from homer.w3.org ([128.30.52.30])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EB7N3-0001i0-H0
	for remoteui@ietf.org; Fri, 02 Sep 2005 04:58:02 -0400
Received: from localhost (homer.w3.org [128.30.52.30])
	by homer.w3.org (Postfix) with ESMTP id 412024EEC6;
	Fri,  2 Sep 2005 04:55:48 -0400 (EDT)
Date: Fri, 2 Sep 2005 09:56:46 +0100 (BST)
From: Dave Raggett <dsr@w3.org>
X-X-Sender: dsr@holly
To: Vlad.Stirbu@nokia.com
Subject: RE: [REMOTEUI] Widex charter proposal draft
In-Reply-To: <1C1F3D15859526459B4DD0A7A9B2268BA0E7F0@trebe101.NOE.Nokia.com>
Message-ID: <Pine.LNX.4.61.0509020952191.10101@holly>
References: <1C1F3D15859526459B4DD0A7A9B2268BA0E7F0@trebe101.NOE.Nokia.com>
X-GPG-PUBLIC_KEY: http://www.w3.org/People/Raggett/pubkey-20040130.asc
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: remoteui@ietf.org
X-BeenThere: remoteui@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Remote UI BoF and future WG discussion list <remoteui.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/remoteui>,
	<mailto:remoteui-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/remoteui>
List-Post: <mailto:remoteui@lists.ietf.org>
List-Help: <mailto:remoteui-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/remoteui>,
	<mailto:remoteui-request@lists.ietf.org?subject=subscribe>
Sender: remoteui-bounces@lists.ietf.org
Errors-To: remoteui-bounces@lists.ietf.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, 2 Sep 2005 Vlad.Stirbu@nokia.com wrote:

> Well, I think that we agreed to have the protocol UI semantic 
> independent and discovery and session setup mechanism independent. 
> We haven't mentioned that the protocol should be transport 
> protocol independent.
>
> In fact, the whole purpose of the working group is to define a 
> single mandatory to implement protocol for synchronising XML DOM 
> events.

So what's wrong with my suggestion that the charter covers defining 
XML message formats and normative bindings to at least SIP, and 
perhaps other protocols?


- -- 
  Dave Raggett <dsr@w3.org>  W3C lead for multimodal interaction
  http://www.w3.org/People/Raggett +44 1225 866240 (or 867351)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFDGBPTb3AdEmxAsUsRAmmdAJ4kjgk8q9wfpCupNJl/YCuURXzktQCgziQt
p9KnCBR4KNhvKPlF8TcPGkQ=
=kMQ6
-----END PGP SIGNATURE-----

_______________________________________________
REMOTEUI mailing list
REMOTEUI@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/remoteui



From remoteui-bounces@lists.ietf.org Fri Sep 02 08:01:41 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EBAEn-0005Ct-3N; Fri, 02 Sep 2005 08:01:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EBAEi-0005BB-Vu
	for remoteui@megatron.ietf.org; Fri, 02 Sep 2005 08:01:37 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01548
	for <remoteui@ietf.org>; Fri, 2 Sep 2005 08:01:36 -0400 (EDT)
From: Vlad.Stirbu@nokia.com
Received: from mgw-ext01.nokia.com ([131.228.20.93])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EBAGr-0008ID-7m
	for remoteui@ietf.org; Fri, 02 Sep 2005 08:03:50 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext01.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id
	j82C1VDq014144; Fri, 2 Sep 2005 15:01:32 +0300
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 2 Sep 2005 15:01:31 +0300
Received: from trebe101.NOE.Nokia.com ([172.22.124.61]) by
	esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 2 Sep 2005 15:01:30 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [REMOTEUI] Widex charter proposal draft
Date: Fri, 2 Sep 2005 15:01:30 +0300
Message-ID: <1C1F3D15859526459B4DD0A7A9B2268BA0E7F5@trebe101.NOE.Nokia.com>
Thread-Topic: [REMOTEUI] Widex charter proposal draft
Thread-Index: AcWvnDTgk3TAAzKlSjScLrXn3UdF7gAFs7Yw
To: <dsr@w3.org>
X-OriginalArrivalTime: 02 Sep 2005 12:01:30.0619 (UTC)
	FILETIME=[0E25BCB0:01C5AFB6]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Content-Transfer-Encoding: quoted-printable
Cc: remoteui@ietf.org
X-BeenThere: remoteui@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Remote UI BoF and future WG discussion list <remoteui.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/remoteui>,
	<mailto:remoteui-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/remoteui>
List-Post: <mailto:remoteui@lists.ietf.org>
List-Help: <mailto:remoteui-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/remoteui>,
	<mailto:remoteui-request@lists.ietf.org?subject=subscribe>
Sender: remoteui-bounces@lists.ietf.org
Errors-To: remoteui-bounces@lists.ietf.org

LRDP, which is the input document for the RUI BoF, describes the ui =
remoting protocol in terms of a transport protocol (e.g. BEEP) having =
uni-directional channels for exchanging ui synchronisation information =
formatted as XML messages. The document described that you can use the =
ui remoting protocol with several UI representations of user interfaces =
and several discovery and session setup mechanisms, but there were no =
several ui remoting protocols.

If the goal of this working group is to define a single mandatory to =
implement mechanism for synchronizing distributed XML DOM objects, then =
there should be a single transport protocol also.

Vlad

> -----Original Message-----
> From: ext Dave Raggett [mailto:dsr@w3.org]
> Sent: 02 September, 2005 11:57
> To: Stirbu Vlad (Nokia-TP-MSW/Tampere)
> Cc: eburger@brooktrout.com; remoteui@ietf.org
> Subject: RE: [REMOTEUI] Widex charter proposal draft
>=20
>=20
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> On Fri, 2 Sep 2005 Vlad.Stirbu@nokia.com wrote:
>=20
> > Well, I think that we agreed to have the protocol UI semantic=20
> > independent and discovery and session setup mechanism independent.=20
> > We haven't mentioned that the protocol should be transport=20
> > protocol independent.
> >
> > In fact, the whole purpose of the working group is to define a=20
> > single mandatory to implement protocol for synchronising XML DOM=20
> > events.
>=20
> So what's wrong with my suggestion that the charter covers defining=20
> XML message formats and normative bindings to at least SIP, and=20
> perhaps other protocols?
>=20
>=20
> - --=20
>   Dave Raggett <dsr@w3.org>  W3C lead for multimodal interaction
>   http://www.w3.org/People/Raggett +44 1225 866240 (or 867351)
>=20
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (GNU/Linux)
>=20
> iD8DBQFDGBPTb3AdEmxAsUsRAmmdAJ4kjgk8q9wfpCupNJl/YCuURXzktQCgziQt
> p9KnCBR4KNhvKPlF8TcPGkQ=3D
> =3DkMQ6
> -----END PGP SIGNATURE-----
>=20

_______________________________________________
REMOTEUI mailing list
REMOTEUI@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/remoteui



From remoteui-bounces@lists.ietf.org Fri Sep 02 08:49:21 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EBAyu-0001aD-Qb; Fri, 02 Sep 2005 08:49:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EBAys-0001a5-Sb
	for remoteui@megatron.ietf.org; Fri, 02 Sep 2005 08:49:19 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03962
	for <remoteui@ietf.org>; Fri, 2 Sep 2005 08:49:17 -0400 (EDT)
Received: from mgw-ext03.nokia.com ([131.228.20.95])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EBB11-0001WY-6N
	for remoteui@ietf.org; Fri, 02 Sep 2005 08:51:32 -0400
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-ext03.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id
	j82CmWfm025281; Fri, 2 Sep 2005 15:48:33 +0300
Received: from esebh001.NOE.Nokia.com ([172.21.138.28]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 2 Sep 2005 15:49:14 +0300
Received: from [172.21.38.136] ([172.21.38.136]) by esebh001.NOE.Nokia.com
	with Microsoft SMTPSVC(5.0.2195.6881); 
	Fri, 2 Sep 2005 15:49:14 +0300
Message-ID: <43184A49.6080706@nokia.com>
Date: Fri, 02 Sep 2005 15:49:13 +0300
From: Aki Niemi <aki.niemi@nokia.com>
User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Stirbu Vlad (Nokia-TP-MSW/Tampere)" <Vlad.Stirbu@nokia.com>
Subject: Re: [REMOTEUI] Widex charter proposal draft
References: <1C1F3D15859526459B4DD0A7A9B2268BA0E7F5@trebe101.NOE.Nokia.com>
In-Reply-To: <1C1F3D15859526459B4DD0A7A9B2268BA0E7F5@trebe101.NOE.Nokia.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Sep 2005 12:49:14.0219 (UTC)
	FILETIME=[B8FC6BB0:01C5AFBC]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Content-Transfer-Encoding: 7bit
Cc: remoteui@ietf.org
X-BeenThere: remoteui@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Remote UI BoF and future WG discussion list <remoteui.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/remoteui>,
	<mailto:remoteui-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/remoteui>
List-Post: <mailto:remoteui@lists.ietf.org>
List-Help: <mailto:remoteui-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/remoteui>,
	<mailto:remoteui-request@lists.ietf.org?subject=subscribe>
Sender: remoteui-bounces@lists.ietf.org
Errors-To: remoteui-bounces@lists.ietf.org

I think there is a terminology confusion here. I count UDP, TCP and a 
couple of others in the transport protocol category. Anyway, LRDP 
suggests a BEEP profile for transporting the remote UI data, but you 
could as well use SIP events (that itself runs over UDP or TCP).

In fact, defining the event package is really a trivial thing to do; 
SUBSCRIBE is used to initiate a RUI session, NOTIFYs carry the UI markup 
and PUBLISH is used to send in client stimulus.

The used widget markup language (i.e., MIME type) can be negotiated 
using the Accept header field in SIP. Then you can use any service 
discovery to find the SIP resource; an OPTIONS method will tell you 
using the Accept-Events field whether or not the node offers the UI events.

There can certainly be other such protocol bindings, but I agree that 
the SIP event package is a fine one to start with.

Cheers,
Aki

ext remoteui-bounces@lists.ietf.org wrote:
> LRDP, which is the input document for the RUI BoF, describes the ui
> remoting protocol in terms of a transport protocol (e.g. BEEP) having
> uni-directional channels for exchanging ui synchronisation
> information formatted as XML messages. The document described that
> you can use the ui remoting protocol with several UI representations
> of user interfaces and several discovery and session setup
> mechanisms, but there were no several ui remoting protocols.
> 
> If the goal of this working group is to define a single mandatory to
> implement mechanism for synchronizing distributed XML DOM objects,
> then there should be a single transport protocol also.
> 
> Vlad
> 
> 
>> -----Original Message----- From: ext Dave Raggett
>> [mailto:dsr@w3.org] Sent: 02 September, 2005 11:57 To: Stirbu Vlad
>> (Nokia-TP-MSW/Tampere) Cc: eburger@brooktrout.com;
>> remoteui@ietf.org Subject: RE: [REMOTEUI] Widex charter proposal
>> draft
>> 
>> 
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>> 
>> On Fri, 2 Sep 2005 Vlad.Stirbu@nokia.com wrote:
>> 
>> 
>>> Well, I think that we agreed to have the protocol UI semantic 
>>> independent and discovery and session setup mechanism
>>> independent. We haven't mentioned that the protocol should be
>>> transport protocol independent.
>>> 
>>> In fact, the whole purpose of the working group is to define a 
>>> single mandatory to implement protocol for synchronising XML DOM
>>>  events.
>> 
>> So what's wrong with my suggestion that the charter covers defining
>>  XML message formats and normative bindings to at least SIP, and 
>> perhaps other protocols?
>> 
>> 
>> - -- Dave Raggett <dsr@w3.org>  W3C lead for multimodal interaction
>>  http://www.w3.org/People/Raggett +44 1225 866240 (or 867351)
>> 
>> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux)
>> 
>> iD8DBQFDGBPTb3AdEmxAsUsRAmmdAJ4kjgk8q9wfpCupNJl/YCuURXzktQCgziQt 
>> p9KnCBR4KNhvKPlF8TcPGkQ= =kMQ6 -----END PGP SIGNATURE-----
>> 
> 
> 
> _______________________________________________ REMOTEUI mailing list
>  REMOTEUI@lists.ietf.org 
> https://www1.ietf.org/mailman/listinfo/remoteui

_______________________________________________
REMOTEUI mailing list
REMOTEUI@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/remoteui



From remoteui-bounces@lists.ietf.org Fri Sep 02 09:37:28 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EBBjU-0005ln-BL; Fri, 02 Sep 2005 09:37:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EBBjT-0005li-9s
	for remoteui@megatron.ietf.org; Fri, 02 Sep 2005 09:37:27 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06346
	for <remoteui@ietf.org>; Fri, 2 Sep 2005 09:37:25 -0400 (EDT)
Received: from homer.w3.org ([128.30.52.30])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EBBlc-0003Gd-9A
	for remoteui@ietf.org; Fri, 02 Sep 2005 09:39:41 -0400
Received: from localhost (homer.w3.org [128.30.52.30])
	by homer.w3.org (Postfix) with ESMTP id 832CC4EEC6;
	Fri,  2 Sep 2005 09:37:21 -0400 (EDT)
Date: Fri, 2 Sep 2005 14:38:19 +0100 (BST)
From: Dave Raggett <dsr@w3.org>
X-X-Sender: dsr@holly
To: Vlad.Stirbu@nokia.com
Subject: RE: [REMOTEUI] Widex charter proposal draft
In-Reply-To: <1C1F3D15859526459B4DD0A7A9B2268BA0E7F5@trebe101.NOE.Nokia.com>
Message-ID: <Pine.LNX.4.61.0509021336250.10101@holly>
References: <1C1F3D15859526459B4DD0A7A9B2268BA0E7F5@trebe101.NOE.Nokia.com>
X-GPG-PUBLIC_KEY: http://www.w3.org/People/Raggett/pubkey-20040130.asc
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Cc: remoteui@ietf.org
X-BeenThere: remoteui@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Remote UI BoF and future WG discussion list <remoteui.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/remoteui>,
	<mailto:remoteui-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/remoteui>
List-Post: <mailto:remoteui@lists.ietf.org>
List-Help: <mailto:remoteui-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/remoteui>,
	<mailto:remoteui-request@lists.ietf.org?subject=subscribe>
Sender: remoteui-bounces@lists.ietf.org
Errors-To: remoteui-bounces@lists.ietf.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I think we are in rough agreement, but this needs to be checked, and 
the charter needs to be elaborated to make explicit the assumptions 
we are working from. Right now, the draft charter while a good 
start, it is lacking in details.

The value in standards is when they are widely implemented, so it is 
important to align with market trends. Furthermore, for mobile and 
embedded devices where the resources are tightly constrained, it 
makes sense to build on top on a protocol that the device already 
needs for other purposes as it is hard to justify a new protocol 
stack. This currently makes BEEP less attractive than SIP and HTTP,
since unlike SIP and HTTP, BEEP is still fairly rare.

Another factor is the prevalance of NAT and firewalls. Consumers 
find it very difficult to configure their gateways to allow incoming 
requests. That makes it desirable to use approaches where the 
initial request is initiated by the client, and once the connection 
is established, messages can move through the gateway in both 
directions. SIP provides a good match to these needs, and that is
why I believe that we should provide bindings to SIP and to account
for how SIP can be used to establish the session via SDP. This is
not to preclude other approaches and I am very interested in you
can provide us with a case for these.

Many devices such as printers now support simple HTTP servers and
this is being taken advantage of when it comes to Web Services.
This allows devices to receive asynchronous messages, but doesn't
work well through consumer gateways. UPnP seems to be more about
identifying the services a device provides than a general means
for supporting remote user interfaces.

In the absence of a stronger candidate, SIP looks like a good
choice for us to adopt.

BTW I am on vacation this coming week and will be back on email
on Monday September 12th.


On Fri, 2 Sep 2005 Vlad.Stirbu@nokia.com wrote:

> LRDP, which is the input document for the RUI BoF, describes the 
> ui remoting protocol in terms of a transport protocol (e.g. BEEP) 
> having uni-directional channels for exchanging ui synchronisation 
> information formatted as XML messages. The document described that 
> you can use the ui remoting protocol with several UI 
> representations of user interfaces and several discovery and 
> session setup mechanisms, but there were no several ui remoting 
> protocols.
>
> If the goal of this working group is to define a single mandatory 
> to implement mechanism for synchronizing distributed XML DOM 
> objects, then there should be a single transport protocol also.
>
> Vlad
>
>> -----Original Message-----
>> From: ext Dave Raggett [mailto:dsr@w3.org]
>> Sent: 02 September, 2005 11:57
>> To: Stirbu Vlad (Nokia-TP-MSW/Tampere)
>> Cc: eburger@brooktrout.com; remoteui@ietf.org
>> Subject: RE: [REMOTEUI] Widex charter proposal draft
>>
>>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On Fri, 2 Sep 2005 Vlad.Stirbu@nokia.com wrote:
>>
>>> Well, I think that we agreed to have the protocol UI semantic
>>> independent and discovery and session setup mechanism independent.
>>> We haven't mentioned that the protocol should be transport
>>> protocol independent.
>>>
>>> In fact, the whole purpose of the working group is to define a
>>> single mandatory to implement protocol for synchronising XML DOM
>>> events.
>>
>> So what's wrong with my suggestion that the charter covers defining
>> XML message formats and normative bindings to at least SIP, and
>> perhaps other protocols?

- -- 
  Dave Raggett <dsr@w3.org>  W3C lead for multimodal interaction
  http://www.w3.org/People/Raggett +44 1225 866240 (or 867351)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFDGFXQb3AdEmxAsUsRAsDQAJ48piCJ3IqXwRxnO5m9trs5JzhxDACfUX4F
XgP7UqmieWZD4rBNYRwpQIg=
=cL02
-----END PGP SIGNATURE-----

_______________________________________________
REMOTEUI mailing list
REMOTEUI@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/remoteui



From remoteui-bounces@lists.ietf.org Tue Sep 06 13:32:18 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EChIw-0006A1-0U; Tue, 06 Sep 2005 13:32:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EChIu-00069U-2S
	for remoteui@megatron.ietf.org; Tue, 06 Sep 2005 13:32:16 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09101
	for <remoteui@ietf.org>; Tue, 6 Sep 2005 13:32:13 -0400 (EDT)
Received: from mgw-ext01.nokia.com ([131.228.20.93])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EChLt-0003Ai-OD
	for remoteui@ietf.org; Tue, 06 Sep 2005 13:35:23 -0400
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-ext01.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id
	j86HW9GN003890; Tue, 6 Sep 2005 20:32:11 +0300
Received: from esebh001.NOE.Nokia.com ([172.21.138.28]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 6 Sep 2005 20:27:12 +0300
Received: from [192.168.1.186] ([10.162.253.221]) by esebh001.NOE.Nokia.com
	with Microsoft SMTPSVC(5.0.2195.6881); 
	Tue, 6 Sep 2005 20:20:16 +0300
Message-ID: <431DCFCD.50303@nokia.com>
Date: Tue, 06 Sep 2005 20:20:13 +0300
From: Aki Niemi <aki.niemi@nokia.com>
User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ext Dave Raggett <dsr@w3.org>
Subject: Re: [REMOTEUI] Widex charter proposal draft
References: <1C1F3D15859526459B4DD0A7A9B2268BA0E7F5@trebe101.NOE.Nokia.com>
	<Pine.LNX.4.61.0509021336250.10101@holly>
In-Reply-To: <Pine.LNX.4.61.0509021336250.10101@holly>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 06 Sep 2005 17:20:16.0512 (UTC)
	FILETIME=[3FB86800:01C5B307]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Content-Transfer-Encoding: 7bit
Cc: Vlad.Stirbu@nokia.com, remoteui@ietf.org
X-BeenThere: remoteui@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Remote UI BoF and future WG discussion list <remoteui.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/remoteui>,
	<mailto:remoteui-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/remoteui>
List-Post: <mailto:remoteui@lists.ietf.org>
List-Help: <mailto:remoteui-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/remoteui>,
	<mailto:remoteui-request@lists.ietf.org?subject=subscribe>
Sender: remoteui-bounces@lists.ietf.org
Errors-To: remoteui-bounces@lists.ietf.org


ext Dave Raggett wrote:
> I think we are in rough agreement, but this needs to be checked, and the 
> charter needs to be elaborated to make explicit the assumptions we are 
> working from. Right now, the draft charter while a good start, it is 
> lacking in details.

I agree, or at least the details need a bit of refinement.

> The value in standards is when they are widely implemented, so it is 
> important to align with market trends. Furthermore, for mobile and 
> embedded devices where the resources are tightly constrained, it makes 
> sense to build on top on a protocol that the device already needs for 
> other purposes as it is hard to justify a new protocol stack. This 
> currently makes BEEP less attractive than SIP and HTTP,
> since unlike SIP and HTTP, BEEP is still fairly rare.

Thinking about this a little more, implementing the actual UI remoting 
using SIP events, while possible, might truly be overkill in what I 
think Vlad's main use case at home is all about. For example, SIP 
mandates support for both UDP and TCP. That seems one too many for a 
light-weight Widex implementation.

> Another factor is the prevalance of NAT and firewalls. Consumers find it 
> very difficult to configure their gateways to allow incoming requests. 
> That makes it desirable to use approaches where the initial request is 
> initiated by the client, and once the connection is established, 
> messages can move through the gateway in both directions. SIP provides a 
> good match to these needs

Needless to say, NAT/FW in SIP does have its share of problems, so this 
isn't probably the strongest argument in favor of SIP.

It seems there are three scenarios that fall into the scope of Widex 
that have something to do with NAT traversal:

1) Server is behind the same NAT/FW device as the client, e.g., at home

2) Server has a globally routable, public IP address (and/or FQDN), and 
the client is behind a NAT device

3) Server is behind a NAT device, and the client is accessing from the 
"outside"

Out of these, I think if the charter addressed 1 and 2, but left 3 for 
further study would mean the working group would address the majority of 
use cases for this work plus guarantee that the WG might actually finish 
one day. ;)

> , and that is
> why I believe that we should provide bindings to SIP and to account
> for how SIP can be used to establish the session via SDP. This is
> not to preclude other approaches and I am very interested in you
> can provide us with a case for these.

Hmm... As the charter says, I think session establishment is not only 
firmly out of scope but also unnecessary, if the remoting protocol is 
sufficiently complete. For example, if the client only needs to know the 
server's address, it could simply connect to that address directly after 
receiving it via some service discovery mechanism.

> Many devices such as printers now support simple HTTP servers and
> this is being taken advantage of when it comes to Web Services.
> This allows devices to receive asynchronous messages, but doesn't
> work well through consumer gateways. UPnP seems to be more about
> identifying the services a device provides than a general means
> for supporting remote user interfaces.

To reiterate, I think the charter should state that the WG works on a 
framework and at least a single remoting protocol that implements the 
framework. There could be others, but LRDP (the BEEP profile based one) 
is the only concrete proposal on the table, and while it probably needs 
some more work, seems like a good starting point.

I think the protocol should be complete in itself so that the only 
"parameter" needed to set up the UI remoting session is the address 
(URI, FQDN, IP address) of the server.

Cheers,
Aki

_______________________________________________
REMOTEUI mailing list
REMOTEUI@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/remoteui



From remoteui-bounces@lists.ietf.org Mon Sep 19 08:23:48 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EHKgW-00028L-Ln; Mon, 19 Sep 2005 08:23:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EHKgU-00027g-FR
	for remoteui@megatron.ietf.org; Mon, 19 Sep 2005 08:23:46 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16509
	for <remoteui@ietf.org>; Mon, 19 Sep 2005 08:23:44 -0400 (EDT)
From: Vlad.Stirbu@nokia.com
Received: from mgw-ext01.nokia.com ([131.228.20.93])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EHKm6-00059h-Mu
	for remoteui@ietf.org; Mon, 19 Sep 2005 08:29:35 -0400
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-ext01.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id
	j8JCNiug022142
	for <remoteui@ietf.org>; Mon, 19 Sep 2005 15:23:44 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 19 Sep 2005 15:23:42 +0300
Received: from trebe101.NOE.Nokia.com ([172.22.124.61]) by
	esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 19 Sep 2005 15:23:16 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [REMOTEUI] Widex charter proposal draft
Date: Mon, 19 Sep 2005 15:23:16 +0300
Message-ID: <1C1F3D15859526459B4DD0A7A9B2268BFF7110@trebe101.NOE.Nokia.com>
Thread-Topic: [REMOTEUI] Widex charter proposal draft
Thread-Index: AcWzBz/X1hdIwQWuSgSArBycY8J8dwKDProw
To: <remoteui@ietf.org>
X-OriginalArrivalTime: 19 Sep 2005 12:23:16.0978 (UTC)
	FILETIME=[E9D20D20:01C5BD14]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Content-Transfer-Encoding: quoted-printable
Cc: 
X-BeenThere: remoteui@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Remote UI BoF and future WG discussion list <remoteui.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/remoteui>,
	<mailto:remoteui-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/remoteui>
List-Post: <mailto:remoteui@lists.ietf.org>
List-Help: <mailto:remoteui-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/remoteui>,
	<mailto:remoteui-request@lists.ietf.org?subject=subscribe>
Sender: remoteui-bounces@lists.ietf.org
Errors-To: remoteui-bounces@lists.ietf.org

Hi,

Attached is the new version of the proposed charter.

Vlad

------------------------------------------------

Description of Working Group

With the Internet reaching out to more and more devices, people are
increasingly expecting to have access to services at anytime, from
anywhere and using any device. Such services are being developed using
Web technologies such as XML and distributed across the network rather
than resident on any one device.

An example is a service to access flight arrival times, where the user
interface expressed in XHTML is rendered on a client device, the
application logic runs on a remote server and a technique as user
interface remoting is used to keep the user interface synchronized with
the application logic. What is currently lacking is a convenient means
for continous fine grained synchronization rather than the one provided
by a request/response protocol (e.g. HTTP) for Web pages, which occurs
in between page loads. This would allow the user interface to reflect
changes in application state and offer greater flexibility for
applications to respond to user input events.

The WiDeX (Widget Description Exchange Service) Working Group seeks to
define a light weight mechanism used in an IP-based network for remoting
user interfaces where the user interface is represented in XML, and
synchronization involves XML DOM events and XML DOM mutation/update
operations.

The WG will strive to preserve an extensible architecture so that the
work possibly be useful in the future with other types of descriptive
user interfaces beyond those specifically considered by the group.

Specific topics that are NOT goals of this WG are:

-	XML representation of user interface objects.
-	Means to establish sessions and support for device coordination.

The WiDeX service definition will define:

-	A mechanism for synchronizing distributed XML DOM objects by
propagating DOM mutations/updates and DOM events.
-	A set of parameters that need to be negotiated by a service
discovery and session setup mechanism in order to start the UI remoting
session.
-	A framework that enables a mechanism for remoting user
interfaces represented in XML format by using distributed XML DOM
synchronization, and a service discovery and session setup mechanism as
building blocks.

Deliverables:

-	Requirements document.
-	Document specifying the framework for remoting user interfaces
represented in XML format.
-	Document specifying the message formats for XML DOM events and
updates using XML in a way that is independent of the transport
protocol.
-	Document(s) specifying normative binding(s) to at least one
transport protocol.

It is possible that work undertaken in other working groups and even
other standards bodies (e.g. W3C) will be referenced by this working
group. It is even possible that entire deliverables could be satisfied
by the work of other working groups (e.g. discovery protocols). This
working group will seek to maximize the use of existing specifications
where applicable.

Goals and Milestones:

Nov. 2005	IETF 64, Charter Working Group
Feb. 2006	Working Group Last Call on Requirements draft
March 2006	IETF 65, Discuss Last Call comments on Requirements
draft
April 2006	Submit Requirements draft to IESG for publication as
Informational RFC
June 2006	Working Group Last Call on Framework, Message Formats
and Transport Bindings drafts
Aug. 2006	IETF 66, Discuss Last Call comments on Framework,
Message Formats and Transport Bindings drafts
Nov. 2006	IETF 67, Submit Framework, Message Formats and Transport
Bindings drafts for publication as Proposed Standard

Internet-Drafts:

LRDP: The Lightweight Remote Display Protocol,
http://www.ietf.org/internet-drafts/draft-stirbu-lrdp-00.txt

_______________________________________________
REMOTEUI mailing list
REMOTEUI@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/remoteui



From remoteui-bounces@lists.ietf.org Tue Sep 20 17:46:51 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EHpwx-0001T6-SP; Tue, 20 Sep 2005 17:46:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EHpwt-0001Py-Oo
	for remoteui@megatron.ietf.org; Tue, 20 Sep 2005 17:46:50 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA08005
	for <remoteui@ietf.org>; Tue, 20 Sep 2005 17:46:44 -0400 (EDT)
Received: from homer.w3.org ([128.30.52.30])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EHq2m-0004RA-O8
	for remoteui@ietf.org; Tue, 20 Sep 2005 17:52:54 -0400
Received: from localhost (homer.w3.org [128.30.52.30])
	by homer.w3.org (Postfix) with ESMTP id 7D6824EECA;
	Tue, 20 Sep 2005 17:46:42 -0400 (EDT)
Date: Tue, 20 Sep 2005 22:46:37 +0100 (BST)
From: Dave Raggett <dsr@w3.org>
X-X-Sender: dsr@holly
To: Vlad.Stirbu@nokia.com
Subject: RE: [REMOTEUI] Widex charter proposal draft
In-Reply-To: <1C1F3D15859526459B4DD0A7A9B2268BFF7110@trebe101.NOE.Nokia.com>
Message-ID: <Pine.LNX.4.61.0509202208040.10078@holly>
References: <1C1F3D15859526459B4DD0A7A9B2268BFF7110@trebe101.NOE.Nokia.com>
X-GPG-PUBLIC_KEY: http://www.w3.org/People/Raggett/pubkey-20040130.asc
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 42e3ed3f10a1d8bef690f09da16f507a
Cc: remoteui@ietf.org
X-BeenThere: remoteui@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Remote UI BoF and future WG discussion list <remoteui.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/remoteui>,
	<mailto:remoteui-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/remoteui>
List-Post: <mailto:remoteui@lists.ietf.org>
List-Help: <mailto:remoteui-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/remoteui>,
	<mailto:remoteui-request@lists.ietf.org?subject=subscribe>
Sender: remoteui-bounces@lists.ietf.org
Errors-To: remoteui-bounces@lists.ietf.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Vlad,

I presented the RemoteUI work at the W3C Multimodal Interaction
working group's face to face meeting (19-21 September 2005), see

   http://www.w3.org/2005/Talks/0919-dsr-remoteui/

One thing that came up was the need for the server to be able
to send events to the UI as well as updates. The UI may have
default event handlers for these events, or such event handlers
may be set via markup or scripts. In some cases the DOM update
messages may not be needed.

Further input from the MMI working group should be available
in mid-October.

I am unsure about the "WiDeX" name, as the protocol isn't really 
about widgets, and I believe that "Widget Description Exchange 
Service" will confuse people since the protocol won't define 
widgets. I understand that "Remote User Interface" may be seen as 
too broad, so it seems like we should continue to look for a more 
apt name than either WiDeX or RemoteUI.

With a view to chartering the working group in time for Vancouver,
it seems like it would be a good idea to get some feedback from
the Area directors on the draft charter, so that we can make any
necessary changes before formally submitting the charter.
Is this an action you could take on?

On Mon, 19 Sep 2005 Vlad.Stirbu@nokia.com wrote:

> Hi,
>
> Attached is the new version of the proposed charter.
>
> Vlad
>
> ------------------------------------------------
>
> Description of Working Group
>
> With the Internet reaching out to more and more devices, people 
> are increasingly expecting to have access to services at anytime, 
> from anywhere and using any device. Such services are being 
> developed using Web technologies such as XML and distributed 
> across the network rather than resident on any one device.
>
> An example is a service to access flight arrival times, where the 
> user interface expressed in XHTML is rendered on a client device, 
> the application logic runs on a remote server and a technique as 
> user interface remoting is used to keep the user interface 
> synchronized with the application logic. What is currently lacking 
> is a convenient means for continous fine grained synchronization 
> rather than the one provided by a request/response protocol (e.g. 
> HTTP) for Web pages, which occurs in between page loads. This 
> would allow the user interface to reflect changes in application 
> state and offer greater flexibility for applications to respond to 
> user input events.
>
> The WiDeX (Widget Description Exchange Service) Working Group 
> seeks to define a light weight mechanism used in an IP-based 
> network for remoting user interfaces where the user interface is 
> represented in XML, and synchronization involves XML DOM events 
> and XML DOM mutation/update operations.
>
> The WG will strive to preserve an extensible architecture so that 
> the work possibly be useful in the future with other types of 
> descriptive user interfaces beyond those specifically considered 
> by the group.
>
> Specific topics that are NOT goals of this WG are:
>
> - XML representation of user interface objects.
> - Means to establish sessions and support for device coordination.
>
> The WiDeX service definition will define:
>
> - A mechanism for synchronizing distributed XML DOM objects by
> propagating DOM mutations/updates and DOM events.
> - A set of parameters that need to be negotiated by a service 
>   discovery and session setup mechanism in order to start the UI 
>   remoting session.
> - A framework that enables a mechanism for remoting user 
>   interfaces represented in XML format by using distributed XML 
>   DOM synchronization, and a service discovery and session setup 
>   mechanism as building blocks.
>
> Deliverables:
>
> - Requirements document.
> - Document specifying the framework for remoting user interfaces
> represented in XML format.
> - Document specifying the message formats for XML DOM events and
> updates using XML in a way that is independent of the transport
> protocol.
> - Document(s) specifying normative binding(s) to at least one
> transport protocol.
>
> It is possible that work undertaken in other working groups and 
> even other standards bodies (e.g. W3C) will be referenced by this 
> working group. It is even possible that entire deliverables could 
> be satisfied by the work of other working groups (e.g. discovery 
> protocols). This working group will seek to maximize the use of 
> existing specifications where applicable.
>
> Goals and Milestones:
>
> Nov. 2005	IETF 64, Charter Working Group
> Feb. 2006	Working Group Last Call on Requirements draft
> March 2006	IETF 65, Discuss Last Call comments on Requirements
> draft
> April 2006	Submit Requirements draft to IESG for publication as
> Informational RFC
> June 2006	Working Group Last Call on Framework, Message Formats
> and Transport Bindings drafts
> Aug. 2006	IETF 66, Discuss Last Call comments on Framework,
> Message Formats and Transport Bindings drafts
> Nov. 2006	IETF 67, Submit Framework, Message Formats and Transport
> Bindings drafts for publication as Proposed Standard
>
> Internet-Drafts:
>
> LRDP: The Lightweight Remote Display Protocol,
> http://www.ietf.org/internet-drafts/draft-stirbu-lrdp-00.txt
>
> _______________________________________________
> REMOTEUI mailing list
> REMOTEUI@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/remoteui
>

- -- 
  Dave Raggett <dsr@w3.org>  W3C lead for multimodal interaction
  http://www.w3.org/People/Raggett +44 1225 866240 (or 867351)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFDMINBb3AdEmxAsUsRAgj+AKCRZwgvGU34AbRTG0lCxeUAklOvMgCfbR5I
b1m+7XrXPpGLHsI458JJIjE=
=lWLa
-----END PGP SIGNATURE-----

_______________________________________________
REMOTEUI mailing list
REMOTEUI@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/remoteui



