- From: Anssi Kostiainen <anssi.kostiainen@nokia.com>
- Date: Mon, 21 May 2012 11:33:50 +0300
- To: Dzung D ext Tran <dzung.d.tran@intel.com>, Doug Turner <dougt@mozilla.com>, ext Marcos Caceres <w3c@marcosc.com>
- Cc: ext Jonas Sicking <jonas@sicking.cc>, "public-device-apis@w3.org public-device-apis@w3.org" <public-device-apis@w3.org>
Hi All, On 18.5.2012, at 15.07, ext Anssi Kostiainen wrote: > 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. Given no concerns were raised, I updated the spec as I outlined above to clear up the confusion: http://dvcs.w3.org/hg/dap/raw-file/tip/proximity/Overview.html This should address all the issues discussed on the list. If there are any other issues, let us know. Dzung - could you redirect the userproximity.html fork to this draft? Thanks! -Anssi
Received on Monday, 21 May 2012 08:34:37 UTC