RE: Issue-39: Tracking of Geographic Data

Karl,

Agreed - these are also forms of Inferred ___location - albeit weaker as its difficult to ascertain if a user is searching for their current destination (less common) versus a ___location they are interested in learning more about (more common).

The Map example is more of a "declared" form of ___location and falls someone where closer to the registration or user-provided use case.

In either example, these are not by-products of cross-site tracking.

- Shane

-----Original Message-----
From: Karl Dubost [mailto:karld@opera.com] 
Sent: Wednesday, December 14, 2011 8:18 AM
To: Shane Wiley
Cc: Jeffrey Chester; public-tracking@w3.org
Subject: Re: Issue-39: Tracking of Geographic Data


Le 14 d�c. 2011 � 10:06, Shane Wiley a �crit :
> c.       Inferred:  Based on generally the IP Address, a map is created to devise the geo-___location of the user/agent (quality/confidence erodes as granularity increases)

repeated queries of the same search terms, 
repeated queries of a "from: ___location" in a map direction scenario, etc.
There are many ways to inferred a ___location from a user. 

The ___location is also a strong identifier for scoping the profiling of someone. For example, when you tie statistics about type of residents in certain areas of the city, be in terms of resources levels, religious beliefs, races, countries of origins, etc. This gives more information about the type of consumers you might reach.

-- 
Karl Dubost - http://dev.opera.com/
Developer Relations & Tools, Opera Software

Received on Wednesday, 14 December 2011 17:00:30 UTC