RE: [Widex] Proposed rewording for Framework draft

> The bullet point needs to be read in the context of the preceding
> paragraph:
> 
>   The Widex Framework needs a mechanism by which the Widex Renderer
>   determines which events have a remote scope and therefore need to
>   be serialized and forwarded to the Widex Server.  The determination
>   of  which events have a remote scope could be achieved in one of
>   three ways:
> 
>     o  prior agreement between the Widex Renderer and Widex Server
>     o  a list of events passed during session establishment
>     o  the Widex Server could direct the Widex Renderer to add
>        and remove event listeners during the session
> 
> This I believe makes it pretty clear that what is being discussed
> are events that are raised in the Windex Renderer and which need to
> be forwarded to the Widex Server as WO.Event messages. The bullet
> point suggests that one way for the Widex Server to indicate which
> such events it is interested in is via a list of events that is
> exchanged with the Widex Renderer at session establishment. Widex
> won't define the events, but it is within our scope to define a
> mechanism for passing a list of event names as part of session
> establishment for a binding to specific protocol. This is something
> we can now start talking about in more detail, but it would be
> good to first reach agreement on publishing the framework draft.

Ok, I see, the word "event" here indeed means "UI event". But it's not really
sending event, as in the WO.Event messages. Here, we are talking about
exchanging a list of event names. So maybe change it to "a list of event names"?

Regards,

Jin
________________________________________
Jin Yu
OpenXUP.org

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