Cancel DAP call this week, meet next Thursday 19 Sept; pls work on ISSUES and ACTIONS on mail list

I think we need more list work before having the next call, so the DAP call is cancelled this week.

Please plan for a teleconference next week on Thursday at 10am ET (same time as usual but Thursday instead of Wednesday) - please send regrets in advance if necessary.

In the meantime we have ISSUES for Vibration that need resolution as well as discussion. Please use the list for this. 

For Network Service Discovery can we  resolve ISSUE-151 on the list? (as well as maybe others?)

Publication of  the Network Service Discovery WD is still in progress and should happen soon.

Please also review your actions below and post any updates to the list.

Thanks

regards, Frederick

Frederick Hirsch
Nokia

Open ISSUES:

ISSUE-128 : Need more description on how bandwidth should be estimated ; on [Network Information API] http://www.w3.org/2009/dap/track/issues/128 

ISSUE-130 : Enable variety of protocols (e.g. UPnP, Bonour) with protocol independent developer code ; on [Network Service Discovery] http://www.w3.org/2009/dap/track/issues/130 

ISSUE-131 : Support UPnP device discovery by Device Type? ; on [Network Service Discovery] http://www.w3.org/2009/dap/track/issues/131 

ISSUE-133 : Fix UPnP events subscription and unsubscription ; on [Network Service Discovery] http://www.w3.org/2009/dap/track/issues/133 

ISSUE-134 : Rename NetworkServices and NetworkService events ; on [Network Service Discovery] http://www.w3.org/2009/dap/track/issues/134 

ISSUE-146 : Add vibration strength control ; on [Vibration API] http://www.w3.org/2009/dap/track/issues/146 

ISSUE-147 : Reference 'Requirements for Home Networking Scenarios' in Introduction ; on [Network Service Discovery] http://www.w3.org/2009/dap/track/issues/147 

ISSUE-148 : NetworkService.name definition in 8.2.2.4 incoherent with definition in 7.1 (a human-readable title for the service) ; on [Network Service Discovery]http://www.w3.org/2009/dap/track/issues/148 

ISSUE-149 : handling of long vibration list - truncate or no vibration at all ; on [Vibration API] http://www.w3.org/2009/dap/track/issues/149 

ISSUE-150 : Should vibration be additive when multiple instances, e.g. iframes ; on [Vibration API] http://www.w3.org/2009/dap/track/issues/150 

ISSUE-151 : USN should not be used as device identifier ; on [Network Service Discovery] http://www.w3.org/2009/dap/track/issues/151 

open ACTIONS:

ACTION-523: Anssi Kostiainen to Work on test cases for battery, vibration, and HTML Media Capture

ACTION-642: Dominique Hazaël-Massieux to Review proximity and ambient light test cases

ACTION-645: Frederick Hirsch to Share Network Service Discovery editors draft with PING

ACTION-652: Anssi Kostiainen to Make proposal on list regarding multiple vibration api invocations in frames for vibration

ACTION-654: Jean-Claude Dufourd to Propose text for network service discovery to define wildcard api and feature detection

ACTION-655: Anssi Kostiainen to Update test for light :https://dvcs.w3.org/hg/dap/rev/916dbd5920d8

ACTION-656: Anssi Kostiainen to Update proximity test for https://dvcs.w3.org/hg/dap/rev/a6ad49819c41

ACTION-657: Anssi Kostiainen to Revise battery tests for idlharness, find qa person to help

--end--

Received on Tuesday, 10 September 2013 14:38:17 UTC