I'm trying to solve the problem you described here with twitterplaces. 1. You tweet about L:placename 2. You go to twitterplaces.com/username/placename and specify the exact address (address is guessed from google local search) 3. Other apps can request twitterplaces.com/username/placename.json to access the location address.
So, a small piece of infrastructure like bit.ly - is the plan. :) Ben On Jun 21, 4:27 pm, "Dean Collins" <[email protected]> wrote: > Although it might be nice and easy to go for just L:NAME what happens when > there are more than 1 café with the same name? > > How do I tell what country you are in? > > How do I tell the date/relevance to me etc. > > It's notlocationspecific but we've been using the term CHurl - to indicate a > live Chat URL. Basically we setup the following for our baseball fan site > (which is connected to twitter via API) > > http://www.livebaseballchat.com/CHurl/06-21-2009/1019/479 > > Made up of the following constitute parts > > URL/ LiveBaseballChat.com (we are going to launch 7 more so needed the > name included) > > CHurl/ Word > > 06/ Month > > 21/ Date > > 09/ Year > > 1019/ Room number > > 479/ Message number > > Regards, > > Dean Collins > Live Chat Concepts Inc > [email protected] > +1-212-203-4357 New York > +61-2-9016-5642 (Sydney in-dial). > +44-20-3129-6001 (London in-dial). > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of benn > Sent: Friday, June 19, 2009 10:07 PM > To: Twitter Development Talk > Subject: [twitter-dev]Tagsfor places? > > What's a good tag-type to use for when a user refers to places? I've been > using $dollartags and then indexing them - eg "off to $mojocoffee for MORE > BEANS". Are there any standards for these already? I've seen people using L: > styletags. > > Any other recommendations for tag semantics for places? > > Ben > twitterplaces.com
