Re: Re: Bookmark 'stability'
"Eric J. Bowman" <[email protected]>
| Newsgroups | gmane.comp.web.services.rest |
|---|---|
| Organization | Bison Systems Corporation |
| Message-ID | <[email protected]> |
"[email protected]" wrote: > > Indeed, the server cannot control whether a URI is bookmarked or not, > but it should definitely advertise its capabilities. In this case, > the capability of maintaining a URI as an entry point for resource X > "forever". > I have no idea where participants in this thread are getting this notion. In the case of an excerpt of one document appearing in another, rel='bookmark' identifies a permalink, is all. When appearing in the <head> of a transient message, say a purchase confirmation from a shopping cart, it can give the UA a permalink to the order in the CRM system, in lieu of the current URI, if the user bookmarks the receipt. > > The only resource that has the bookmark contract from the start is > the API's entry point (root). For the rest, may them be of type > bookmark or not, the client needs to know the freedoms and > responsibilities it has for bookmarking them. > I know of no such contract. Nor does REST endorse an "entry point" for any API. I see a whole lot in this thread that folks are reading in to REST, which is really neither here nor there. To be continued... -Eric