Hi Jan Yes, exactly - URLs are for browsing (or, for the restafarians, "CRUDing", I suppose). They are not for crediting, debiting, instantiating, booking, confirming, eating, watering, ...
And with respect to your other responses, I probably didn't make myself clear in my last email - sorry. The examples I gave were just that: examples. Yes, of course you can do more with books than write or read them. And similarly, pizzas and flowers can be dealt with in many different ways. What I was trying to say is that operations such as "read" or "write" are to all intents and purposes meaningless unless you know what you are reading or writing. In fact, REST provides a relevant illustration of this. HTTP GET (the REST equivalent of "read") is quite a different thing to reading a book, and HTTP POST (the REST equivalent of "write") to writing one! My argument is that you can't decouple verbs and nouns - operations and domains - since some people in the preceding debate were suggesting this would be a worthwhile aim for SOA design. -- All the best Keith http://keith.harrison-broninski.info Jan Algermissen wrote: >On Feb 26, 2006, at 12:20 PM, Keith Harrison-Broninski wrote: > > >>but attempting to separate interface from semantics is not a useful >>approach, imho. >> >> >How many Web sites have you accessed through your browser yesterday? >Did they have different semantics (Google, Amazon, Ordering a Pizza, >performing a bank transaction,..)? And was it helpful the their APIs >are uniform and you could do all this with a single browser? > >Imagine how much more difficult that would be if each service had >its own interface! > >Cheers, > >Jan > Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
