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

[admin] Agenda (v2) - DAP Distributed Meeting 13 November 2014

From: Frederick Hirsch <w3c@fjhirsch.com>
Date: Thu, 13 Nov 2014 09:45:26 -0500
Message-Id: <29172C04-8C56-4D72-961C-F8C5DBAB59C0@fjhirsch.com>
Cc: Frederick Hirsch <frederick.hirsch@nokia.com>
To: W3C Device APIs WG <public-device-apis@w3.org>
Agenda — Device APIs Working Group — Distributed Meeting 13 November 2014, 10-11 ET; meeting details at end of email.

(minor updates: corrected link for status on DAP work on sensors, added Battery/Vibration API items, note on wake lock, health care breakout)

Please not that the focus of this meeting is a discussion on Generic Sensor API following 10 minutes of DAP review.

If anyone can volunteer as scribe in advance, please let me know

1) Welcome, agenda review, scribe selection, announcements, status updates

Scribe selection

wake lock status - http://lists.w3.org/Archives/Public/public-device-apis/2014Nov/0010.html

health care TPAC breakout summary - http://lists.w3.org/Archives/Public/public-device-apis/2014Nov/0007.html

2) Battery API

CfC for transitioning and publishing Battery API as CR completed successfully, http://lists.w3.org/Archives/Public/public-device-apis/2014Nov/0012.html

3) Vibration API

CfC for transitioning and publishing Vibration API as PR completed successfully, http://lists.w3.org/Archives/Public/public-device-apis/2014Nov/0013.html

4) Minutes approval

Approve minutes from 2 October 2014


proposed RESOLUTION: Minutes from 2 October 2014 are approved

5) Generic Sensor API: Context, problem statement, goals (Anssi, Mounir)

[As outlined in the SessionIdeas wiki, see https://www.w3.org/wiki/TPAC2014/SessionIdeas#Generic_Sensor_API ]

In addition to fixing the known issues with the current APIs, another goal I’ve identified is to evaluate the feasibility of specifying a generic sensor API with no dependencies on web related concepts.

To draw parallels, WHATWG Streams is currently agnostic to the environment, implementable in both the browser and Node.js environments. W3C Streams API extends the WHATWG spec to meet the requirements specific to the browser environment. Can we do the same for sensors, i.e. the base Generic Sensor API spec remains multi-environment, while the abstractions on top (concrete sensors) may be specific to the environment (but do not need to)?

6) Generic Sensor API:  Related work in W3C, current status  

4a) DAP work on sensors; see http://www.w3.org/2009/dap/wiki/SingleSensorSpecification (Frederick)

4b) Geolocation WG; Geolocation API, Device Orientation

5) Generic Sensor API Proposal review - Sensor API Unification Sketch (Rick)

Generic Sensor API proposal and related Node.js implementation experiences


6) Generic Sensor API Proposal review - Tim Volodine's proposal 


7) Generic Sensor API - Other Proposals

8) Generic Sensor API - Summary, Discussion and Next Steps

At the end of the session, we should have an understanding whether there’s rough consensus to move to the next steps with a Generic Sensor API.

9) Other Business

10) Adjourn

Meeting Details:

Zakim Bridge: +1.617.761.6200, +, or +44.117.370.6152
Conference code: 3279 ("DAPW", or "EASY")
IRC channel: 

Instructions on meetings : 

regards, Frederick

Frederick Hirsch, Nokia
Chair, W3C DAP Working Group

Generic Sensor breakout,  see https://www.w3.org/wiki/TPAC2014/SessionIdeas#Generic_Sensor_API

A number of sensors are already exposed to the Web Platform (e.g. Geolocation, Device Orientation) and new sensors are on their way (e.g. Ambient Light) -- however, each API looks and feels different. Is this an issue, and if yes, how to fix that?

Currently, there is no established design pattern for sensor APIs on the Web Platform. Meanwhile, outside the browser-land, the Node.js community has defined and implemented composable APIs for exposing new sensors rapidly. Can we learn from each other? In this session we discuss the known issues of the current sensor APIs on the Web Platform and review the recent concrete proposals for sensor API unification (see background materials). Example open questions: should we decouple the sensor APIs from the window object to make it feasible to implement the APIs in other contexts outside browsers (e.g. Node.js, Internet/Web of Things)?

The generic sensor API deliverable is in scope for the W3C Device APIs Working Group, but the concrete specification work has not yet started. Come join our session, and influence the direction of this potential new work item.

	• Type: open discussion
	• Background materials:
		• Sensor API Unification Sketch by Rick Waldron
		• Tim Volodine's proposal
Received on Thursday, 13 November 2014 14:46:27 UTC

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