- From: Marcos Caceres <w3c@marcosc.com>
- Date: Fri, 18 May 2012 13:37:25 +0100
- To: Anssi Kostiainen <anssi.kostiainen@nokia.com>
- Cc: ext Jonas Sicking <jonas@sicking.cc>, Doug Turner <dougt@mozilla.com>, Dzung D ext Tran <dzung.d.tran@intel.com>, "public-device-apis@w3.org public-device-apis@w3.org" <public-device-apis@w3.org>
On Friday, May 18, 2012 at 1:07 PM, Anssi Kostiainen wrote: > Hi Jonas, Doug, Dzung, All, > > Thanks for the excellent feedback! Now it looks like we should go with the second option. The use case that caused concerns is still valid, but it is not feasible to implement, it seems. I assume Doug is soon able to share his experiences based on running code, which should clear things up too. > > Spec-wise, I interpret we should take the following concrete actions: > > * Specify both the instances of proximity -- the "device proximity" and the "user proximity" -- similarly in the same draft. All the infrastructure is shared, so it makes sense (e.g. deviceorientation and devicemotion are spec'd together too). Only security and privacy considerations may differ. This would also make the lives of the editors a bit easier, which is a bonus :) > > * The current "Device proximity" section would be copied over to the current "User proximity" section, the interfaces renamed s/Device/User/g. The event interface would only have a single attribute 'near' of type boolean. > > All - let me know if you have concerns with this plan. Otherwise, we'll start updating the draft with Dzung as outlined above: > > http://dvcs.w3.org/hg/dap/raw-file/tip/proximity/Overview.html > > If there's no immediate agreement, we may wait for the next week's call before proceeding. > Sounds like a plan. Let me know if you need any Editorial support or need another round of review after the update. -- Marcos Caceres
Received on Friday, 18 May 2012 12:38:00 UTC