ºÝºÝߣ

Editor's Notes

• #2: - who here runs a website? - who here uses location of some kind on their website? - mobile?
• #6: - location is a proxy to lots of metadata - rich demographic data - context about the physical surroundings of the user - events they might be at - nearby POIs - time of day, weather
• #7: - the more context you have the more relevant the experience you can delivery
• #8: - deliver the most highly relevant experience to your users - use most accurate location available
• #9: (seth) There’s no single right answer.
• #10: (seth) Are Ryan and I in the same place? Yes and no. The definition of a place is highly relative. Place names as well.
• #11: (seth) Where on Earth ids are one solution.
• #12: (seth) GeoPlanet is Yahoo!’s answer to the “what constitutes a place” problem. Places are referred to with unique identifiers and related to one another. It’s just one approach, but it helps.
• #14: (seth) Complementary approaches, complementary tools. Sensed location is device-centric, declared location requires the user’s input. Active location is a means for determining where a user is when s/he is in front of a computer. Passive location is a means for determining where a user is when s/he is away from a computer, but has a device that can sense location with them (e.g. SPOT, cell phone).
• #15: Sensed location is the more obvious approach, and potentially most useful, as it involves less user intervention. However, it is not without problems: sensed locations may be wrong, and, as location is a socially relative construct, may disrupt or offend the user. (e.g. neighborhood boundaries)
• #20: - relevancy. too much noise, not enough signal - location is a piece of metadata that can make the entire web more relevant - better user experience - geotag photos, share location on social networks, local search, local news
• #21: - Lets take a store finder as an example - each dot represents a Dunkin Donuts in Boston - if you ask a user to tell you where they are, they will say “boston” or “02218” - using precise location allows you to instantly show them the correct location and start to route them there
• #22: - seth 1. privacy 2. precision
• #23: (seth) A user’s location is a facet of their identity; they are sharing it with you (or allowing you to sense it) in exchange for something of value. They trust you. It’s your responsibility to respect your users by not sharing it out, or being explicit about what you intend to do with it once it passes into our hands.
• #24: (seth) Precision is one way to protect a user’s location; just request the level of granularity that your application requires rather than always asking for a user’s exact location. You probably don’t need it, and it will give your users a greater sense of safety when using your application.
• #26: - June 2008 - standardize the way geolocation is exposed through the browser
• #27: - all major vendors are involved - already getting to draft - KISS
• #28: “its all coming together”
• #30: - instead of waiting for all the browsers, add it now - cross platform, cross browser - on MapQuest.com/findme
• #31: (ryan) - Here is a video of BrightKite using auto-location - gives you a feel for how other sites are doing it (seth) - imagine brightkite updating while you’re out in the world and sharing it with friends who are online; a single application can take advantage of both active and passive location
• #40: Fire Eagle is a location broker; alone it does nothing. It is part of a rich ecosystem where applications with access to users’ location can allow them to share it with applications that would like access to location data. Privacy is core: users have control over what applications can do what with their location (and what level they’re allowed to see).
• #46: - if you are looking to get more involved in geo, there are some great events to attend