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 -Brandon On Wed, Apr 23, 2008 at 4:18 PM, Kristian Thy <[EMAIL PROTECTED]> wrote: > On Wed, Apr 23, Sean Gillies wrote: > > > L:Placename: or L:lon, lat: > > > > And if you were very large and polygonal, would you use GML or GeoJSON? > > Since twitter is rather informal, wouldn't a bbox do? > > L:minx,miny,maxx,maxy :) > > \\kristian > -- > ... et nemo ex vobis interrogat me: »Quo vadis?« > _______________________________________________ > Geowanking mailing list > [email protected] > http://lists.burri.to/mailman/listinfo/geowanking >
_______________________________________________ Geowanking mailing list [email protected] http://lists.burri.to/mailman/listinfo/geowanking
