RE: [agenda] Protocol Use Cases

I’m not quite sure what distinguishes a *protocol* use case.  But I offer the following three use cases, which are directly relevant to work that I am involved with.

 *   Cover Art. A “Cover Art” annotation asserts that a particular image is cover art for a particular book or version of a book.  Thus the body is an image and the target is a resource description of a book (or particular version of the book).
 Use Case: Hennepin County Library acquires an eBook copy of Shakespeare's Macbeth. The library wishes to find cover art that it can use to advertise its copy. (Either there was no cover art supplied with the copy, or the cover art supplied was not deemed satisfactory.) There are dozens or perhaps hundreds of cover art images for Macbeth. For many of these images, someone (either the artist, or a third-party annotator) has created an annotation saying "this image is cover art for this version". The Library can search cover art Annotations and select one that it likes.
 *   Holdings.  A “Holding” annotation asserts that a particular library holds a copy of a particular item (e.g. book).  Thus the body is a structured description of the holding, including the holding library, its location, call number of the item, access conditions, etc.  The target is a resource description of the item.
 Use Case: Lucy is looking for a copy of the book Plum Island, by DeMille. She would like to find a local library that holds a copy, within her town of Independence Missouri. She searches by title and finds the resource description. Holding Annotations are attached to it, and she discovers that Blue River Library has a copy, which she is able to borrow.
 *   Reviews. A “review” annotation asserts that a particular resource is a review for a particular book.
Use Case: Amy is trying to determine whether she wants to read the book Shining Girls by Beuke; she would like to read reviews. There are many reviews - at Goodreads, Amazon, NY Times, NPR, and various other web sites. Amy would prefer to be able to gather a list of links to reviews, rather than going to each review site individually to look for a review of the book. Any reviewer is of course free to post a review to whatever review site he/she chooses. However, if, when a review is written, an Annotation can be created saying "this is a review of this book", then Amy can search for review Annotations and find at least those reviews for which Annotations exist.
Ray

From: Robert Sanderson [mailto:azaroth42@gmail.com]
Sent: Thursday, November 13, 2014 6:21 PM
To: Web Annotation
Subject: [agenda] Protocol Use Cases


Dear all,

In order to move forwards in parallel with the different deliverables that we're chartered to produce, it would be great to discuss Use Cases on next week's call, particularly for the Protocol deliverable to inform discussions with other working groups, including both the Social Web WG, and the LDP WG which is starting to recharter and needs input as to what should be included in their next iteration.

Use Cases for the Interface and Anchoring components are also important, and we should also discuss those towards defining scope and requirements.  My sense is that these are a little more specialized compared to the need to transfer annotations between systems, and hence starting with protocol is likely the easiest route forwards.

Rob & Frederick

--
Rob Sanderson
Technology Standards Advocate
Stanford University
Stanford, CA 94305