Considerations for web service URL interface

[AaronAcerboni]

Web service url structure

What is the best URL structure for creating a query-able interface for the noodle web service?

Below are some of examples:

.com/fetch/halfmelt.com
.com/fetch?q=halfmelt.com
.com/html?q=halfmelt.com&selector=a[href]
.com/json?q=foo.json&selector=a.b
.com/multiple/?q=html;halfmelt.com;selector=.foo,.bar|rss;foo.com;selector=blah

Queries can be quite complex as they could contain characters which should be encoded as well as multiple values for one key. eg extract=html,href,text

Multiple queries can also be sent within one request. These queries could be delimited by a | character. The Google charts API makes use of the pipe delimitations for their urls.