W3C home > Mailing lists > Public > public-device-apis@w3.org > February 2014

[admin] Agenda - Distributed Meeting 6 February 2014

From: <Frederick.Hirsch@nokia.com>
Date: Wed, 5 Feb 2014 21:37:31 +0000
To: <public-device-apis@w3.org>
CC: <Frederick.Hirsch@nokia.com>
Message-ID: <A3FFF71C-F39B-4949-BC79-2EDC9990086A@nokia.com>
Agenda  Device APIs Working Group  Distributed Meeting 6 February 2014

Meeting details at the bottom of this email.

1) Welcome, agenda review, scribe selection, announcements


2) Minutes approval

Approve minutes from 30 January 2014

http://lists.w3.org/Archives/Public/public-device-apis/2014Jan/att-0056/minutes-2014-01-30.html

proposed RESOLUTION: Minutes from  30 January 2014 are approved

3) Network Service Discovery

Editors update; plans to publish updated WD

Schedule for LC?

4) Vibration

CfC for publishing LC completes today, plan to publish Tuesday, 11 Feb. please respond to CfC on list.

CfC: http://lists.w3.org/Archives/Public/public-device-apis/2014Jan/0055.html

publication draft: http://dev.w3.org/2009/dap/vibration/LC3.html

5) Standby API Specification proposal

http://lists.w3.org/Archives/Public/public-device-apis/2014Feb/0001.html

6) 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-666: Giridhar Mandyam to Check with internal implementers whether vibration api is consistent with chip capabilities

ACTION-679: Frederick Hirsch to Arrange publication of vibration LC 3

Pending actions

ACTION-674: Frederick Hirsch to Open cfc for lc publication of vibration once ACTION-673 completed

ACTION-678: Anssi Kostiainen to Prepare lc draft of vibration with publication date 4 feb, lc end 25 feb, updated status, link,validity and pub rules check

7) 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-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-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 

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
Received on Wednesday, 5 February 2014 21:38:28 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:54:02 UTC