On Wed, Apr 23, 2008 at 7:42 PM, Brandon Martin-Anderson <[EMAIL PROTECTED]> wrote: > In the case of coordinates you're going to want to specify the projection so > > l:epsg,minx,miny,maxx,maxy oh crap we've done it again and crufted up a > minimalist protocol > > --==-- > > Seriously though I propose ">location" where "location" is a name in your > personal namespace or an absolute coordinate. Locations in other uses's > namespaces are referred to as "@user>home". hash-tags can have namespaces > too so "#wherecamp>cafeteria" means something. Locations for yourself are > read/write, users are read-only, and locations for hashtags are read/write. > You can import locations from other namespaces or from an absolute > coordinate system with "@self>[EMAIL PROTECTED]>location". > > To set the meaning of "office" in the namespace "officenomads", import that > location into my own namespace as "work" and then set my location to "work" > > #officenomads>office=1617 Boylston Ave,Seattle > @ewedistrict>work=#officenomads>office > >work > > This would work too: > > #officenomads>office=1617 Boylston Ave,Seattle > >#officenomads>office > > Or simply > > >1617 Boylston Ave,Seattle > > Oh nevermind this is all too silly >
You have some good points - and this originally came up on geowanking a little over a year ago. However, the issue here is momentum. There was also some work with the Microformats community: http://microformats.org/wiki/picoformats There are a number of apps using L: already, even though I totally agree it's too many keystrokes and there is no way to bound the location information. (e.g. "Heading to L:Portland to enjoy some beer") The best way to address this would be to work with the MF community to get a format accepted that then propagated to the broader dev/app world. > > On Thu, Apr 24, 2008 at 1:37 AM, Mikel Maron <[EMAIL PROTECTED]> wrote: > It looks like > lat*lng*message > > And the very simple advantage is that this takes about 20 less keystrokes on > some phones. But minus the fact that I typically don't know my Lat & Lon off the top of my head (unless I'm Jack Bauer/24) > > > I also heard today that Twitter added an API method to change a users > location, > though I haven't found any documentation. From here, it's not far to API > methods to locate each tweet. > Ryan's got you covered: http://www.sarver.org/2008/04/23/twitter-adds-profile-geolocation-api/ _______________________________________________ Geowanking mailing list [email protected] http://lists.burri.to/mailman/listinfo/geowanking
