Fwd: WG Action: Widget Description Exchange Service (widex)
bradh at frogmouth.net
Tue Oct 25 01:25:14 BST 2005
This is from the Internet Engineering Task Force. This may be of interest to
some of you - a standardised way of doing XML user interface management over
a network. See below for more details on what is / is not in scope.
For those who haven't played in the IETF before, the way it works is that you
join the mailing list, and argue about the technical details (so its a lot
like KDE, except for the lack of code). There is no such thing as corporate
or organisational membership in the IETF working groups - only individuals.
---------- Forwarded Message ----------
Subject: WG Action: Widget Description Exchange Service (widex)
Date: Tuesday 25 October 2005 06:04 am
From: IESG Secretary <iesg-secretary-reply at ietf.org>
To: IETF Announcement list <ietf-announce at ietf.org>
Cc: remoteui at ietf.org, Dean Willis <dean.willis at softarmor.com>
A new IETF working group has been formed in the Application Area.
For additional information, please contact the Area Directors or the WG
Widget Description Exchange Service (widex)
Current Status: Active Working Group
Dean Willis <dean.willis at softarmor.com>
Applications Area Director(s):
Ted Hardie <hardie at qualcomm.com>
Scott Hollenbeck <shollenbeck at verisign.com>
Applications Area Advisor:
Scott Hollenbeck <shollenbeck at verisign.com>
General Discussion: remoteui at ietf.org
To Subscribe: https://www1.ietf.org/mailman/listinfo/remoteui
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
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.
- 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
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
Goals and Milestones:
Nov 05 Charter Working Group
Feb 06 Working Group Last Call on Requirements draft
Mar 06 Discuss Last Call comments on Requirements draft
Apr 06 Submit Requirements draft to IESG for publication as Informational
Jun 06 Working Group Last Call on Framework, Message Formats and Transport
Aug 06 Discuss Last Call comments on Framework, Message Formats and
Transport Bindings drafts
Nov 06 Submit Framework, Message Formats and Transport Bindings drafts for
publication as Proposed Standard
IETF-Announce mailing list
IETF-Announce at ietf.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
More information about the kde-core-devel