Anne Thomas Manes wrote: > GET http://example.org/customer/anne <http://example.org/customer/anne> > returns a representation of "anne" > > GET http://example.org/customer/personByName?name=anne > <http://example.org/customer/personByName?name=anne> > returns a representation of "anne" > or perhaps returns the URI of the "anne" resource > or perhaps returns a list of URIs of all people named "anne" > might also be specified more simply as > GET http://example.org/customer?name=anne > <http://example.org/customer?name=anne>
Saying there's a distinction where one of those URLs is less ambiguous than the other is a gensym fallacy. http://example.org/customer/anne http://example.org/customer/personByName?name=anne are equally ambiguous. Pete Lacey made a similar point here recently about methods: "Ahh, but you're assuming that order_lunch means ordering lunch. In my interface order_lunch causes the resource to be deleted. ;-) My not-as-funny-as-I-thought way of saying the actual names of the methods aren't important, just the definition of those methods in that interface's spec." > POST http://example.org/company <http://example.org/company> > HTTP message body contains a representation of "newco" > server creates a subordinate resource called > http://example.org/company/newco <http://example.org/company/newco> Yes, noting that the usual way to signify the URL of the new resource is in the header Location with a 201 Created response. cheers Bill
