Re: [Widex] Proposed rewording for Framework draft

Rosfran Lins Borges <rosfran.borges@indt.org.br> Thu, 22 June 2006 00:19 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FtCux-0000k0-6C; Wed, 21 Jun 2006 20:19:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FtCuv-0000do-SO for widex@ietf.org; Wed, 21 Jun 2006 20:19:29 -0400
Received: from mgw-ext12.nokia.com ([131.228.20.171]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FtCuu-0001o5-EC for widex@ietf.org; Wed, 21 Jun 2006 20:19:29 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213]) by mgw-ext12.nokia.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id k5M0JQ5Z025708; Thu, 22 Jun 2006 03:19:27 +0300
Received: from daebh102.NOE.Nokia.com ([10.241.35.112]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 22 Jun 2006 03:19:26 +0300
Received: from daebe102.NOE.Nokia.com ([10.241.35.115]) by daebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 21 Jun 2006 19:19:24 -0500
Received: from [172.19.141.56] ([172.19.141.56]) by daebe102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 21 Jun 2006 19:19:22 -0500
Message-ID: <4499DFF1.7070603@indt.org.br>
Date: Wed, 21 Jun 2006 21:10:25 -0300
From: Rosfran Lins Borges <rosfran.borges@indt.org.br>
Organization: INdT/Recife
User-Agent: Debian Thunderbird 1.0.7 (X11/20051017)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ext Dave Raggett <dsr@w3.org>
Subject: Re: [Widex] Proposed rewording for Framework draft
References: <000901c69414$f052c1d0$1e02a8c0@martsbs.local> <Pine.LNX.4.62.0606200940170.8780@localhost.localdomain>
In-Reply-To: <Pine.LNX.4.62.0606200940170.8780@localhost.localdomain>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 22 Jun 2006 00:19:22.0958 (UTC) FILETIME=[83238EE0:01C69591]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: Vlad.Stirbu@nokia.com, widex@ietf.org
X-BeenThere: widex@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Working list for the WIDEX working group at IETF <widex.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/widex>, <mailto:widex-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/widex>
List-Post: <mailto:widex@ietf.org>
List-Help: <mailto:widex-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/widex>, <mailto:widex-request@ietf.org?subject=subscribe>
Errors-To: widex-bounces@ietf.org

     After reading all the recent discussions, and reviewing again the 
Widex framework draft, I would like to suggest a better rephrasing to 
the last paragraph from section 4.2:

"4.2.  WO.Event Message

    The WO.Event messages are primarily used to carry events triggered on
  (...)
    interface.

    Note: Some UI markup languages, e.g.  Glade [1], do not have events
    defined at document level and therefore WO.Event messages MUST be
    able to serialize the events emitted by the associated libraries,
    e.g.  GTK+ [2]."


Would changes to:

    "Note: Some UI markup languages, e.g.  Glade [1], which are 
originally designed for only working with standalone UI architectures 
(i.e., that doesn't implements a networked MVC, where we have a 
change-propagation mechanism that ensures consistency between 
remotelly-located user interface and model), and do not have a defined 
syntax for event modeling (at least, not at document level), this kind 
of UI event was not originally made to be carried as a string of bits 
through the network. So, when using Widex with these applications, the 
WO.Event messages MUST be able to serialize the events (where "events" 
would means "GTK+ signals") emitted by its associated UI libraries, e.g. 
GTK+ [2]."


-- 
Rosfran Borges

_______________________________________________
Widex mailing list
Widex@ietf.org
https://www1.ietf.org/mailman/listinfo/widex