public-device-apis@w3.org from September 2013 by subject

[admin] Reminder of Patent Policy for Non-member Contributions

[discovery] Updated WD of Network Service Discovery published

[light] CfC concluded to progress Ambient Light Events to CR

[proximity] CfC concluded to progress Proximity Events to CR

[proximity] Should names used in Proximity specification be changed?

[vibration] How to handle iframes?

Agenda - Distributed Meeting 19 Sept 2013 (Thursday)

Agenda - Distributed Meeting 26 Sept 2013 (Thursday)

Agenda - Distributed Meeting 4 Sept 2013

ambient lights and proximity test suites now in github master

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

CfC: transition and publish Light Events as CR, respond by 5 September

CfC: transition and publish Proximity Events as CR, respond before 5 September

DAP-ISSUE-131:　A proposal for supporting UｎP Device discovery

DAP-ISSUE-148: NetworkService.name definition in 8.2.2.4 incoherent with definition in 7.1 (a human-readable title for the service) [Network Service Discovery]

DAP-ISSUE-149: handling of long vibration list - truncate or no vibration at all [Vibration API]

DAP-ISSUE-150: Should vibration be additive when multiple instances, e.g. iframes [Vibration API]

DAP-ISSUE-151: USN should not be used as device identifier [Network Service Discovery]

Draft Minutes 4 Sept 2013

Draft minutes DAP 19 Sept 2013 teleconference

ISSUES-131: Support UPnP device discovery by Device Type?

Minutes 26 Sept 2013

NSD API security

Plan to transition Web Notifications spec to LCWD

Test cases submitted for HTML Media Capture

Use <friendlyName> as a human-readable title for UPnP service

Vibration API strength (weaker/stronger)

Last message date: Thursday, 26 September 2013 23:11:57 UTC