- From: Mark Nottingham <mnot@yahoo-inc.com>
- Date: Thu, 1 Jun 2006 10:09:12 -0700
- To: Paul Denning <pauld@mitre.org>
- Cc: public-web-http-desc@w3.org
+1 - I've seen these situations come up. On 2006/06/01, at 9:20 AM, Paul Denning wrote: > > http://esw.w3.org/topic/WebDescriptionUseScenarios?highlight=% > 28CategoryWebDescription%29 > > Other use scenarios that come to mind: > > 1. Comparing descriptions of two API's. For example, scuttle may > claim to implement some/all of the del.icio.us API. > 2. Ability to mark a subset of an existing API; again, for > example, to show what subset of the del.icio.us API another similar > service implements. > > I find myself using a few social bookmarking systems: public > (del.icio.us), corporate intranet, work group (when the corporate > implementation chokes on some bookmarks). > > I use bookmarklets and firefox extensions that work with one API > (i.e., del.icio.us), and I want to adapt them to work with the > other services. This involves a comparison of what API subset a > tool (bookmarklet, browser extension) uses and what API subset an > alternative service implements. > > Another interesting aspect of interface description is > redirection. For example, [1] will redirect to [2]. > > [1] http://del.icio.us/url/?url=http%3A%2F%2Fesw.w3.org%2Ftopic% > 2FFrontPage > [2] http://del.icio.us/url/0d7a759146fad6ec8652c08cfcba98cc > > Paul > > > -- Mark Nottingham mnot@yahoo-inc.com
Received on Thursday, 1 June 2006 17:11:30 UTC