From remoteui-bounces@lists.ietf.org Wed Jun 29 15:30:59 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DniGx-0001Vk-M7; Wed, 29 Jun 2005 15:30:59 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DniGw-0001Va-DA for remoteui@megatron.ietf.org; Wed, 29 Jun 2005 15:30:58 -0400 Received: from mgw-ext04.nokia.com (mgw-ext04.nokia.com [131.228.20.96]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29180 for ; Wed, 29 Jun 2005 15:30:56 -0400 (EDT) From: Basavaraj.Patil@nokia.com Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145]) by mgw-ext04.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id j5TJQJrW032454 for ; Wed, 29 Jun 2005 22:26:23 +0300 Received: from daebh102.NOE.Nokia.com ([10.241.35.112]) by esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 29 Jun 2005 22:30:53 +0300 Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by daebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 29 Jun 2005 14:30:45 -0500 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 Date: Wed, 29 Jun 2005 14:30:44 -0500 Message-ID: <456943D540CFC14A8D7138E64843F8530129D774@daebe101.NOE.Nokia.com> Thread-Topic: Charter or BoF Thread-Index: AcV84QsbFcGBBYgRQN6hDxePM+9oBQ== To: X-OriginalArrivalTime: 29 Jun 2005 19:30:45.0424 (UTC) FILETIME=[0B9CD300:01C57CE1] Content-Transfer-Encoding: quoted-printable Cc: Subject: [REMOTEUI] Charter or BoF X-BeenThere: remoteui@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Remote UI BoF and future WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: remoteui-bounces@lists.ietf.org Errors-To: remoteui-bounces@lists.ietf.org Hi Vlad, Can you post the charter of the Remote UI BoF to the list? Thx. -Raj _______________________________________________ REMOTEUI mailing list REMOTEUI@lists.ietf.org https://www1.ietf.org/mailman/listinfo/remoteui From remoteui-bounces@lists.ietf.org Thu Jun 30 03:24:28 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DntPP-0000y1-V8; Thu, 30 Jun 2005 03:24:27 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DntPP-0000xr-6K for remoteui@megatron.ietf.org; Thu, 30 Jun 2005 03:24: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 DAA11986 for ; Thu, 30 Jun 2005 03:24:25 -0400 (EDT) From: Vlad.Stirbu@nokia.com Received: from mgw-ext03.nokia.com ([131.228.20.95]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Dntp6-0002LT-G0 for remoteui@ietf.org; Thu, 30 Jun 2005 03:51:01 -0400 Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143]) by mgw-ext03.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id j5U7LTLD011483 for ; Thu, 30 Jun 2005 10:21:30 +0300 Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 30 Jun 2005 10:24:17 +0300 Received: from trebe101.NOE.Nokia.com ([172.22.124.61]) by esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 30 Jun 2005 10:24: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="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Thu, 30 Jun 2005 10:24:15 +0300 Message-ID: <1C1F3D15859526459B4DD0A7A9B2268BA0E6C1@trebe101.NOE.Nokia.com> Thread-Topic: Remote UI BoF description Thread-Index: AcV9RLmD3D2Y4KzJSiab0UNkGVo4Zg== To: X-OriginalArrivalTime: 30 Jun 2005 07:24:16.0636 (UTC) FILETIME=[B9155BC0:01C57D44] X-Spam-Score: 0.3 (/) X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5 Content-Transfer-Encoding: quoted-printable Cc: Subject: [REMOTEUI] Remote UI BoF description X-BeenThere: remoteui@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Remote UI BoF and future WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: remoteui-bounces@lists.ietf.org Errors-To: remoteui-bounces@lists.ietf.org Remote UI BoF (rui) ------------------- CHAIRS Vlad Stirbu TBA DESCRIPTION: The Remote UI is a mechanism that enables user interfaces to be rendered = on other devices than those that run the application logic. Manufacturers are creating devices that are highly optimised for certain = environments. Because the devices are intended for a diverse range of = purposes,=20 their UI capabilities can vary considerably; screen size and ratio, = color depth,=20 windowing system with various widget sets, input methods are making the=20 environment highly heterogeneous. At the same time, application = developers and UI=20 designers are trying to create user interfaces that are high optimised = for the=20 rendering platform, so that the user experience is improved by having = the=20 respective application easy to learn and use. A user interface may be composed of several widgets, wherein a widget is = understood as an element of a user interface that displays information = or=20 provides a specific way for a user to interact with an application. = Widgets may=20 for instance comprise icons, pull-down menus, buttons, selection = buttons,=20 progress indicators, on-off checkmarks, scrollbars, windows, window = edges, toggle=20 buttons, forms and any other elements for displaying information, = inviting,=20 accepting, and responding to user actions. Therefore, when an UI is rendered on another device than the one that is = running the application logic, provisions need to be made, so that the user can = perceive the UI as a local application making it intuitively usable. A widget-level Remote UI protocol provides the mechanism which enable a = client=20 device to generate a UI, received from a server device, using the client = device's=20 native UI capabilities, and keeping the UI synchronised with the = application=20 logic. Typically, a widget-level Remote UI mechanism has usually three = components: - UI description language: contains the descriptions of the widgets, = their=20 properties and relationships between the widgets. Typically the = widget-level=20 UI descriptions are augmented with stylesheets containing hints such as = preferred=20 colours to use, which layout to use, which background picture, etc. - The UI remoting protocol: is the transport protocol that is = responsible with=20 communicating (partial) UI updates from the server to the client and UI = events=20 triggered through changes in widget states made by the user from the = client to=20 the server. - Session setup: is responsible with identifying compatible servers and = clients=20 and initiating the UI remoting session between them. A client is = compatible with=20 a server when they support the same UI remoting protocol and the same UI = description language. GOALS: The goal of the WG is to create a UI remoting protocol for applications = that are=20 using UI Description Languages. AGENDA: - Agenda Bashing (5 min) - Introduction & Background information (10 min) - Problem Statement (60 min) - Possible Solutions (20 min) - Next Steps/WG Charter (10 min) LOGISTICS: Mailing list: remoteui@ietf.org Subscriptions: https://www1.ietf.org/mailman/listinfo/remoteui Internet-Drafts: 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 Thu Jun 30 06:03:10 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dnvt0-0007nc-9Y; Thu, 30 Jun 2005 06:03:10 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dnvsz-0007nU-JW; Thu, 30 Jun 2005 06:03: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 GAA21485; Thu, 30 Jun 2005 06:03:07 -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.33) id 1DnwIi-0001J1-37; Thu, 30 Jun 2005 06:29:45 -0400 Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143]) by mgw-ext04.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id j5U9wR2E025201; Thu, 30 Jun 2005 12:58:30 +0300 Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 30 Jun 2005 13:02:57 +0300 Received: from trebe101.NOE.Nokia.com ([172.22.124.61]) by esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 30 Jun 2005 13:02:53 +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 Date: Thu, 30 Jun 2005 13:02:52 +0300 Message-ID: <1C1F3D15859526459B4DD0A7A9B2268BA0E6C9@trebe101.NOE.Nokia.com> Thread-Topic: Remote UI BoF at IETF63 Thread-Index: AcV9WuFz4fHlCsrgSkuNgmjc3SMpJQ== To: X-OriginalArrivalTime: 30 Jun 2005 10:02:53.0170 (UTC) FILETIME=[E1613520:01C57D5A] X-Spam-Score: 0.3 (/) X-Scan-Signature: 37af5f8fbf6f013c5b771388e24b09e7 Content-Transfer-Encoding: quoted-printable Cc: remoteui@ietf.org Subject: [REMOTEUI] Remote UI BoF at IETF63 X-BeenThere: remoteui@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Remote UI BoF and future WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: remoteui-bounces@lists.ietf.org Errors-To: remoteui-bounces@lists.ietf.org Hi, The attached is the description and agenda of Remote UI BOF (rui) for = IETF63. Those interested are encouraged to attend. Thanks! Regards, Vlad Remote UI BoF (rui) ------------------- CHAIRS Vlad Stirbu TBA DESCRIPTION: The Remote UI is a mechanism that enables user interfaces to be rendered = on other devices than those that run the application logic. Manufacturers are creating devices that are highly optimised for certain = environments. Because the devices are intended for a diverse range of = purposes,=20 their UI capabilities can vary considerably; screen size and ratio, = color depth,=20 windowing system with various widget sets, input methods are making the=20 environment highly heterogeneous. At the same time, application = developers and UI=20 designers are trying to create user interfaces that are high optimised = for the=20 rendering platform, so that the user experience is improved by having = the=20 respective application easy to learn and use. A user interface may be composed of several widgets, wherein a widget is = understood as an element of a user interface that displays information = or=20 provides a specific way for a user to interact with an application. = Widgets may=20 for instance comprise icons, pull-down menus, buttons, selection = buttons,=20 progress indicators, on-off checkmarks, scrollbars, windows, window = edges, toggle=20 buttons, forms and any other elements for displaying information, = inviting,=20 accepting, and responding to user actions. Therefore, when an UI is rendered on another device than the one that is = running the application logic, provisions need to be made, so that the user can = perceive the UI as a local application making it intuitively usable. A widget-level Remote UI protocol provides the mechanism which enable a = client=20 device to generate a UI, received from a server device, using the client = device's=20 native UI capabilities, and keeping the UI synchronised with the = application=20 logic. Typically, a widget-level Remote UI mechanism has usually three = components: - UI description language: contains the descriptions of the widgets, = their=20 properties and relationships between the widgets. Typically the = widget-level=20 UI descriptions are augmented with stylesheets containing hints such as = preferred=20 colours to use, which layout to use, which background picture, etc. - The UI remoting protocol: is the transport protocol that is = responsible with=20 communicating (partial) UI updates from the server to the client and UI = events=20 triggered through changes in widget states made by the user from the = client to=20 the server. - Session setup: is responsible with identifying compatible servers and = clients=20 and initiating the UI remoting session between them. A client is = compatible with=20 a server when they support the same UI remoting protocol and the same UI = description language. GOALS: The goal of the WG is to create a UI remoting protocol for applications = that are=20 using UI Description Languages. AGENDA: - Agenda Bashing (5 min) - Introduction & Background information (10 min) - Problem Statement (60 min) - Possible Solutions (20 min) - Next Steps/WG Charter (10 min) LOGISTICS: Mailing list: remoteui@ietf.org Subscriptions: https://www1.ietf.org/mailman/listinfo/remoteui Internet-Drafts: 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