W3C home > Mailing lists > Public > public-device-apis@w3.org > May 2016

Sensor questions

From: Frederick Hirsch <w3c@fjhirsch.com>
Date: Thu, 26 May 2016 10:43:00 -0400
Cc: "Mandyam, Giridhar" <mandyam@quicinc.com>
Message-Id: <314ED2CB-E79E-4199-9783-33F6D32B153A@fjhirsch.com>
To: W3C Device APIs WG <public-device-apis@w3.org>
I had some sensor questions that I started to ask on the call, but then decided it is better to raise by email, so they are more visible than in minutes. I removed my few notes in the minutes and include them here instead so that I could include a little more detail.

(1) TAG feedback

The TAG feedback about the generic sensor API was generally positive, see Travis notes and log.  Travis also noted that we should consider whether we can work on geolocation using the new generic sensor framework. Thus, to answer Giri's question, I think we should plan for a joint session at TPAC.

What are the remaining next steps related to the TAG feedback?



(2) supporting non-browser use cases (EventTarget)

It sounds like a major use case might be non-browser use, but using EventTarget might be an issue. Where are we on that?

(3) Observables

Given that we don't know the time frame for this ECMAScript language change the plan is to proceed without it, then when it happens evaluate what our next steps might be. Is this correct? (I think this is what Dom said on the call)

(4) Service Workers


where did this conversation end up? Are there any major remaining issues for the generic sensor API?

(5) Permissions

are we going with start or with the constructor or both? Sounds like start is appropriate.

(6) Timestamps


I think the conclusion from Tobie is to always include timestamp. Is that right? Should the issue be closed?


Regards, Frederick

Frederick Hirsch
Received on Thursday, 26 May 2016 14:42:44 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:33:32 UTC