- From: Jean-Claude Dufourd <jean-claude.dufourd@telecom-paristech.fr>
- Date: Thu, 17 Oct 2013 13:37:42 +0200
- To: public-device-apis@w3.org
- Message-ID: <525FCC06.2090700@telecom-paristech.fr>
Regrets for today, teaching. Best regards JC Le 17/10/13 02:02 , Frederick.Hirsch@nokia.com a écrit : > (Reminder, meeting is on Thursday, usual time slot.) > > Agenda — Device APIs Working Group — Distributed Meeting 17 October 2013 > > Meeting details at the bottom of this email. > > 1) Welcome, agenda review, scribe selection, announcements > > UPnP Forum gave final approval status to the SensorManagement device control protocol (DCP) http://lists.w3.org/Archives/Public/public-device-apis/2013Oct/0103.html (Clarke) > > 2) Minutes approval > > Approve minutes from 10 October 2013 > > http://lists.w3.org/Archives/Public/public-device-apis/2013Oct/att-0128/minutes-2013-10-10.html > > proposed RESOLUTION: Minutes from 10 October 2013 are approved > > 3) Proximity and Light > > Updates? > > 4) Vibration > > 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 > > Note question raised by Anssi > > ISSUE-155 : Enable Feature Detection ; on [Vibration API] http://www.w3.org/2009/dap/track/issues/155 > > ACTION-668 > > 5) Note publication > > Updated CfC (ends 29 Oct): http://lists.w3.org/Archives/Public/public-device-apis/2013Oct/0130.html > > 6) Network Service Discovery > > Topics for discussion & resolution? > > Issue review > > 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-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-151 : USN should not be used as device identifier ; on [Network Service Discovery] http://www.w3.org/2009/dap/track/issues/151 > > ISSUE-154 : Security approach ; on [Network Service Discovery] http://www.w3.org/2009/dap/track/issues/154 > > see wiki http://www.w3.org/2009/dap/wiki/NSD_Security > > Web & TV IG review in progress > > PING Review (deferred to follow additional updates) > > 7) Action Review > > http://www.w3.org/2009/dap/track/actions/open > > ACTION-523: Anssi Kostiainen to Work on test cases for battery, vibration, and HTML Media Capture > > ACTION-645: Frederick Hirsch to Share Network Service Discovery editors draft with PING > > ACTION-654: Jean-Claude Dufourd to Propose text for network service discovery to define wildcard api and feature detection > > ACTION-657: Anssi Kostiainen to Revise battery tests for idlharness, find qa person to help > > ACTION-659: Frederick Hirsch to Review web notifications last call specification > > ACTION-660: Anssi Kostiainen to Determine interest in progressing network information api or not > > ACTION-665: Anssi Kostiainen to Update vibration draft per action-652 > > ACTION-666: Giridhar Mandyam to Check with internal implementers whether vibration api is consistent with chip capabilities > > ACTION-668: Anssi Kostiainen to Respond to michael re issue-155 , existing implementations, v2 possibility > > Pending Review > > ACTION-659: Frederick Hirsch to Review web notifications last call specification > > ACTION-663: Frederick Hirsch to Respond regarding issue-153 that it is closed > > ACTION-664: Frederick Hirsch to Respond indicating issue-152 deferred, suggesting more detailed use case/requriements for v.next > > ACTION-667: Frederick Hirsch to Draft note corresponding to resolution > > ACTION-669: Frederick Hirsch to Send CfC to publish Notes for shelved drafts with WD publications in TR > > 8) Other Business > > 9) Adjourn > > Meeting Details: > > Zakim Bridge: +1.617.761.6200, +33.4.89.06.34.99, or +44.117.370.6152 > Conference code: 3279 ("DAPW", or "EASY") > IRC channel: > irc://irc.w3.org:6667/dap > > Instructions on meetings : > http://www.w3.org/2009/dap/#meetings > > regards, Frederick > > Frederick Hirsch, Nokia > Chair, W3C DAP Working Group > > > > > -- Télécom ParisTech <http://www.telecom-paristech.fr> *Jean-Claude DUFOURD <http://jcdufourd.wp.mines-telecom.fr>* Directeur d'études Tél. : +33 1 45 81 77 33 37-39 rue Dareau 75014 Paris, France Site web <http://www.telecom-paristech.fr>Twitter <https://twitter.com/TelecomPTech>Facebook <https://www.facebook.com/TelecomParisTech>Google+ <https://plus.google.com/111525064771175271294>Blog <http://jcdufourd.wp.mines-telecom.fr>
Received on Thursday, 17 October 2013 11:38:13 UTC