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

Re: [sensors] the near/far event names

From: Marcos Caceres <w3c@marcosc.com>
Date: Mon, 14 May 2012 15:38:04 +0100
Message-ID: <4FB118CC.1020708@marcosc.com>
To: "SULLIVAN, BRYAN L" <bs3131@att.com>
CC: "Tran, Dzung D" <dzung.d.tran@intel.com>, "public-device-apis@w3.org" <public-device-apis@w3.org>
On 14/05/2012 15:32, SULLIVAN, BRYAN L wrote:
> Ok, when the user is in front of the laptop at typical distance, the Webapp will enable a video feed. When the user moves away, the Webapp can disable the feed. Similar control can be applied to the mic (audio mediastream).
How is that not far/near (again, you failed to show how "min, max, 
value" come into play)? Also, distance from computer mic would not 
affect the gain (I could speak louder as I move away)... and mic could 
be attached to me (e.g., a headset).

> Thanks,
> Bryan Sullivan
>
> On May 14, 2012, at 4:03 PM, "Marcos Caceres" <w3c@marcosc.com> wrote:
>
>> On 14/05/2012 14:48, SULLIVAN, BRYAN L wrote:
>>> I was echoing the use case pointed out by Dzung, ie the user is using a laptop, and the very close proximity assumptions of a mobile phone don't apply (unless you wanted to use the proximity sensor to know that a laptop has been closed). In the user proximity case the developer may want to know specifically how far the user is, if such is supported by sensors.
>> What problem is the developer wanting to solve by knowing the precise distance from the user to the device (i.e., in terms of min, max, value VS near/far)? With all due respect, the above is not a use case. A use case would be something like "If the developer knows that the user is X value away, then the developer can do the following things:". No one has presented "the following things" yet, specially as they relate to "min, max, value" VS "near/far" (apart to working out near/far!).
>>
>> So, again, can you tell me what you (Bryan) would do with min, max, value if you had access to it?
>>
Received on Monday, 14 May 2012 14:38:39 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 14 May 2012 14:38:39 GMT