- From: Alissa Cooper <acooper@cdt.org>
- Date: Fri, 31 Oct 2008 17:58:18 -0400
- To: Andrei Popescu <andreip@google.com>
- Cc: public-geolocation <public-geolocation@w3.org>
Hi Andrei,
On Oct 29, 2008, at 11:03 PM, Andrei Popescu wrote:
> On Wed, Oct 29, 2008 at 9:46 PM, Alissa Cooper <acooper@cdt.org>
> wrote:
>>
>> Handling the event of a position request would then take two
>> arguments
>> instead of one -- the position and the usage rules:
>>
>> interface PositionCallback {
>> void handleEvent(in Position position, in UsageRules
>> usageRules);
>> };
>>
>> If the position obtained from the host does not come in the form of a
>> Geopriv object, the UA would use the default rules or prompt the
>> user for
>> rules. If the position object is a Geopriv object, the UA would set
>> (and
>> comply with) the rules as they already exist in the object.
>>
>
> If I understand this right, you are proposing that a client (e.g. a
> Web page) using the API would also get a UsageRules object, in
> addition to the Position object. Further to Ian's question, could you
> please clarify how would the client be constrained to obey the rules
> in the UsageRules object?
The client would not be constrained to obey the rules any more than a
food finder is currently constrained to use the velocity that the
Position object conveys to it (which I'm guessing most food finders
don't use) or any more than a friend finder is currently constrained
to use the altitude accuracy that the Position object conveys to it
(which I'm guessing goes unused as well). Every client is not going to
use every piece of data it receives via an API call. But that doesn't
mean sending that data is not worthwhile for clients that will make
use of the data.
Alissa
Received on Friday, 31 October 2008 21:58:58 UTC