- From: Frederick Hirsch <w3c@fjhirsch.com>
- Date: Sun, 23 Nov 2014 14:45:57 +0100
- To: "Denenberg, Ray" <rden@loc.gov>
- Cc: Frederick Hirsch <w3c@fjhirsch.com>, Web Annotation <public-annotation@w3.org>
- Message-Id: <6ABE7D6E-0B40-479D-A662-C42BFF426481@fjhirsch.com>
Ray What I read from your email is the following issue: issue: define discovery mechanism for annotations associated with a given target I would not expect the data model to define discovery mechanism, nor general protocol definitions. This is another aspect that may require use cases and definitions; however not in immediate charter scope [1], so probably v.next issue Even if all is localized, we seem to have enough to do :) does this all make sense? regards, Frederick Frederick Hirsch, Nokia Co-Chair W3C Web Annotation WG @fjhirsch [1] http://www.w3.org/annotation/charter/ On Nov 18, 2014, at 6:26 PM, Denenberg, Ray <rden@loc.gov> wrote: > I am not clear on what we mean when we talk about protocol with respect to annotations. > > In my view of the world of annotations, ProviderX has a database of resources, for example, journal articles. UserA reads an article and creates an annotation. That annotation is a resource created on some annotation database that userA has access to create an annotation on (obviously, not on ProviderX’s database). UserB (unrelated to UserA) comes across that article and want to see annotations of the article. > > How does UserB discover UserA’s annotation (or for that matter any annotation of that article)? UserB doesn’t even know of the existence of UserA and his/her annotation database. > > Is this what we mean (or part of what we mean) by annotation protocol? > > Pardon the naïve question but I don’t see this addressed in the model. It is something I’ve wondered about for quite a while and don’t have an answer. But I speculate that part of the process is that when UserA creates the annotation, ProviderX is somehow notified of its creation and can choose to point to that annotation, and then UserB can find it. > > Is this issue addressed anywhere in any greater detail than this vague description? Or is this to be part of the “protocol” to be developed. > > Apologies if this has all been addressed and solved, and I just can’t find it. > > Ray
Received on Sunday, 23 November 2014 13:46:56 UTC