[Openstreetmap-dev] REST

[Tom Carden]

I should add that I have heard the flickr api referred to as not really 
being RESTful, since it doesn't really specify URIs for things and 
GET/PUT/POST/DELETE them.  I'm aware of that, and I'm aware that the methods 
I suggested below look more like RPC methods than REST.

Hopefully someone else can point us in the right direction?  Until we get to 
representing the modification history of the maps, would GPX be a sufficient 
format?

Tom.

----- Original Message ----- 
From: "Tom Carden" <tom at tom-carden.co.uk>
To: "SteveC" <steve at fractalus.com>; <openstreetmap-dev at vr.ucl.ac.uk>
Sent: Monday, July 18, 2005 2:17 PM
Subject: Re: [Openstreetmap-dev] REST


> SteveC wrote:
>> If we threw away the xmlrpc and had things RESTful
>>
>> http://en.wikipedia.org/wiki/Representational_State_Transfer
>>
>> would that make people happy or sad?
>>
>
> Both.  Happy because there would be less fluff over the wire (XML-RPC is 
> uglee), and Sad because I don't know of a neat REST library which just 
> bungs things into generic types in Java, and parsing XML the way I do it 
> makes the baby Jesus cry.
>
> I've only ever used the Flickr REST API (which now has a complicated but 
> interesting authentication API too).  http://www.flickr.com/services/api 
> Any others we should be aware of?  (Anyone used the google API or the 
> Amazon API?)
>
> Initial thoughts...
>
> Needed for the applet, yesterday:
>
> http GETs...
> getTracks which takes a lat-lon bounding box, and returns a list of 
> available gps point collections (date, user, count)
> getPoints which takes a lat-lon bounding box, date, user, perpage and 
> pagenumber, and returns a list of gps points (in GPX format?)
> getNodes which takes a lat-lon bounding box, and returns a list of nodes
> getLines which takes a list of node ids, and returns a list of lines (and 
> optional metadata?)
> getLinesWithNodes which takes a lat-lon bounding box and a token, and 
> returns a list of lines with nodes and locations and metadata.  Hopefully 
> in a way which could be parsed as a stream.
>
> http POSTs (or PUTs or DELETEs?)...
> addNode which takes a lat/lon and a token and gets back an id
> addLine which takes two node ids and a token and gets back an id
> setMeta which takes a line id and a key value pair
> deleteNode which takes an id and a token and also removes any lines 
> involved
> deleteLine which takes an id and a token
>
> Not sure how these should be named exactly, or what the returned XML data 
> would look like.  Perhaps where possible we could return gpx data?  e.g. 
> getNodes (waypoints), getTracks (trksegs), etc.
>
> All off the top of my head...
>
> Tom.
>
>
> _______________________________________________
> Openstreetmap-dev mailing list
> Openstreetmap-dev at vr.ucl.ac.uk
> http://bat.vr.ucl.ac.uk/cgi-bin/mailman/listinfo/openstreetmap-dev