Having a per-page link to get an alternate representation of a
resource is certainly helpful for some applications, and please do
support it, but don't consider the problem solved.
The primary weakness of this approach is that it works only if a page
is dedicated to a single resource.
COinS are still needed, in particular in situations in which multiple
resources are displayed on a page (like, for instance, in the search
results pages of most online systems or on pages such as
http://citeulike.org, or in a list of references such as in the
"references" section of many Wikipedia pages.)
- Godmar
On Mon, Dec 1, 2008 at 11:21 PM, Ed Summers <[log in to unmask]> wrote:
> On Mon, Dec 1, 2008 at 11:05 PM, Karen Coyle <[log in to unmask]> wrote:
>> I asked about COinS because it's something I have vague knowledge of. (And I
>> assume it isn't too difficult to implement.) However, if there are other
>> services that would make a bigger difference, I invite you (all) to speak
>> up. It makes little sense to have this large quantity of bib data if it
>> isn't widely and easily usable.
>
> Sorry to be overwhelming. I guess the main thing I wanted to
> communicate is that you could simply add:
>
> <link rel="alternate" type="application/json"
> href="http://openlibrary.org/api/get?key=/b/{open-library-id}" />
>
> to the <head> element in OpenLibrary HTML pages for books, and that
> would go a long way to making machine readable data for books
> discoverable by web clients.
>
> //Ed
>
