I will just add (again) to the request for all links. As Jonathan says the client can then decide what to show, how to group them, and so on.
I had rather sloppily elided things like format of full text into my "structural" information about the link.
And second the request that some simple coding (controlled vocabulary anyone?) is used for these values so that we clients can determine what we are seeing.
Thanks - Peter
> -----Original Message-----
> From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of
> stuart yeates
> Sent: Tuesday, March 30, 2010 18:20
> To: [log in to unmask]
> Subject: Re: [CODE4LIB] Works API
> Jonathan Rochkind wrote:
> > Karen Coyle wrote:
> >> The OL only has full text links, but the link goes to a page at the
> >> Internet Archive that lists all of the available formats. I would
> >> prefer that the link go directly to a display of the book, and offer
> >> other formats from there (having to click twice really turns people
> >> off, especially when they are browsing). So unfortunately, other than
> >> "full text" there won't be more to say.
> > In an API, it would be _optimal_ if you'd reveal all these links, tagged
> > with a controlled vocabulary of some kind letting us know what they are,
> > so the client can decide for itself what to do with them (which may not
> > even be immediately showing them to any user at all, but may be
> > analyzing them for some other purpose).
> Even better, for those of us who have multiple formats of full text (TEI
> XML, HTML, ePub, original PDF, reflowed PDF, etc) expose multiple URLs
> to the full text, differentiated using the mime-type.
> Stuart Yeates
> http://www.nzetc.org/ New Zealand Electronic Text Centre
> http://researcharchive.vuw.ac.nz/ Institutional Repository