Rough Notes from WIDEX at IETF 64

Reported by Jerry Shih

• Widex wg first meeting

• IPR rules were read by the chair

• Agenda was agreed with no comments

• Charter scope read by chair with no comments

• Charter mission read by chair with no comments

• Deliverables

o Req doc

o Framework

o Message format

o Bindings to at least one transport

• Current milestones: see charter page

• Annocumencemtts

o New mailing list widex@ietf.org next week

• TODO: Scott: update the supplemental webpage; chair will do it

• Jabber scribe: no

• Widex req presentation

o User interface is defined as XML DOM

o Simple and complex user interfaces

o Remote user interface Objects are: update, mutation and event

o Asking for WG adoption

• TODO: Ted?: Different scenario on ipv4 and ipv6 interworking needs to be considered

• Noted that Both session integrity and privacy should be provided by security measure

• Noted from Eric: Another BOF (XML-patch) is looking at the similar thing; promoting the req to a general solution? The charter doesn’t require to address the general solution.

• Noted from Eric: Avoid targeting a specific application that might undermine the powerful ietf transport capability. 

• Noted from Jerry: The relationship with the OMA DS activity? Eric: SyncML is static and not do Events that is what makes this different

• Noted that: Motion to adopt as WG document: agreed

• Presentation on multimodal MMI architecture: (w3c)

• Question: does the existing req addresses Messaging order and reliability. The WG will make sure it does.

• Noted on Binding messages: W3C comments indicate we may need to indicate which DOM tree or XML document is the target of each WIDEX event. Do we need to put this into each event, or do we have a binding between a WIDEX session and a single document such that the session context conveys this information?

• Note that App is responsible for synchronization

• Do we have a req to provide sync: does app logic captures the user event order within a session for sync? Does this coordination need to be supported between different WIDEX sessions, since a server may have multiple renderers?

• Time based sync? Do we need time coordination for multimodal interactions? Is time-based coordination adequate for the multi-renderer scenarios, given that it implies synchronized clocks?

• Volunteers for more active roles such authorship review and comments; no takers during the meeting.

• Several people volunteered to provide commentary and document review.

• Noted that network latency could provide a problem in sync.

• Noted that Not all the events need to be send to server; some could be handled locally

•