RE: [Widex] Working group last call (WGLC) for Requirements:draft-ietf-widex-requirements-01.txt

"Jin Yu" <jyu@openxup.org> Mon, 15 May 2006 23:18 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FfmKA-0007aQ-Q4; Mon, 15 May 2006 19:18:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FfmK9-0007aL-6S for widex@ietf.org; Mon, 15 May 2006 19:18:01 -0400
Received: from smtp114.sbc.mail.mud.yahoo.com ([68.142.198.213]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FfmK6-0002DM-Nz for widex@ietf.org; Mon, 15 May 2006 19:18:01 -0400
Received: (qmail 14411 invoked from network); 15 May 2006 23:17:58 -0000
Received: from unknown (HELO 3150hw) (jinyu1@sbcglobal.net@64.186.173.202 with login) by smtp114.sbc.mail.mud.yahoo.com with SMTP; 15 May 2006 23:17:57 -0000
From: Jin Yu <jyu@openxup.org>
To: Vlad.Stirbu@nokia.com, widex@ietf.org
Subject: RE: [Widex] Working group last call (WGLC) for Requirements:draft-ietf-widex-requirements-01.txt
Date: Mon, 15 May 2006 16:17:18 -0700
Organization: OpenXUP.org
Message-ID: <000101c67875$b65f8d60$0202fea9@martsbs.local>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <1C1F3D15859526459B4DD0A7A9B2268B02143E91@trebe101.NOE.Nokia.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1807
Thread-Index: AcZ0jmffaPtnBu+qSUW0vT/v89333QCpATFwAFAhbMA=
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Cc:
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

Hi Vlad,

My comments are based on reading both the January framework draft and the
April requirement draft. So I agree with you that the comments might be a
bit too detailed for the requirements draft, and indeed they may be more
appropriate for the framework draft.

Regards,

Jin
________________________________________
Jin Yu
OpenXUP.org

> -----Original Message-----
> From: Vlad.Stirbu@nokia.com [mailto:Vlad.Stirbu@nokia.com]
> Sent: Sunday, May 14, 2006 10:46 AM
> To: jyu@openxup.org; widex@ietf.org
> Subject: RE: [Widex] Working group last call (WGLC) for
> Requirements:draft-ietf-widex-requirements-01.txt
> 
> Hi Jin,
> 
> We started the requirements draft with the goal of having a minimal set
> of requirements that a system exporting the UI to another system must
> fulfill but stop short of going deeper in describing the system. Having
> these goals in mind we described the high level interactions between the
> Widex Server and Widex Renderer as having just two basic interfaces:
> 
> a) update interface, used to send information from the server to the
> renderer that is basically generated by the application logic;
> b) event interface, used to send information from the renderer to the
> server that is basically generated by the user interaction with the
> rendered UI.
> 
> It is quite likely that the terms used so far in the requirements draft
> will not map directly to the specification, as is the case with the
> proposed Widex framework
> (http://www.ietf.org/internet-drafts/draft-stirbu-widex-framework-00.txt
> ) where practically all messages exchanged between the Widex Server and
> the Widex Renderer are events described using REX.
> 
> I think that being able to dynamically adjust which events server is
> interested in is a good feature but that is a design issue and Dave
> already mentioned several alternatives. We'll have to asses these
> alternatives and select the optimal one for our environment.
> 
> As a bottom line, I think that your comments are very useful but I think
> that they should be considered for the Widex Framework draft rather than
> for the Requirements.
> 
> Regards,
> Vlad


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