W3C home > Mailing lists > Public > public-openannotation@w3.org > June 2014

Re: Annotations which notify of changes

From: Robert Sanderson <azaroth42@gmail.com>
Date: Fri, 20 Jun 2014 12:24:07 -0700
Message-ID: <CABevsUHgtWiGxu3hA2p1mqkaTPOUCOWfAOauNmw2_ULC2otNcg@mail.gmail.com>
To: Patrick Cuba <cubap@slu.edu>
Cc: public-openannotation <public-openannotation@w3.org>
Hi Patrick,

It's certainly not crazy, and I don't know of a solution other than the
ResourceSync option that Herbert describes.
I think this would be a great use case to take forwards to the API
component of the W3C Working Group discussion, not only between systems but
also at an internal level so that we have a robust event system within a
client side (e.g. javascript) API for browsers.

Thanks!

Rob



On Tue, Jun 17, 2014 at 3:09 PM, Patrick Cuba <cubap@slu.edu> wrote:

> context: OAC (and SharedCanvas and IIIF) in web applications for
> manuscript studies using linked open data structures.
>
> *Annotation update notification service:*
>
> Is there a place in a spec for an annotation which carries an endpoint
> with it to notify about updates? Certainly not all annotation stores or
> applications would honor this, but if they did it may improve the lives of
> large repositories that share much of their data.
>
> For example:
> <anno> a oa:Annotation ;
> eg:onUpdate "example.com/anno-notify" .
>
> When someone (some machine) updates this annotation, the new annotation
> URI can be sent to the endpoint where it would be consumed by some service
> so the watcher would know something happened.
>
> Perhaps for a cleaner world, there is a separate digital object that is a
> Notifier like:
> <Notifier> a eg:Notification ;
> eg:watches <anno> ;
> eg:onUpdate "example.com/anno-notify" ;
> eg:onTargeted "example.com/anno-notify" ;
> eg:onEmbodied "example.com/anno-notify" .
>
> If I support it, I can look for these Notifiers on the graph when I make
> changes or a store may register them independently if Stanford decides to
> start following whose publicly using their manifests without just sending a
> robot out for a stroll every once in an iteration.
>
> I imagine a public annotation store can do this outside of standards
> without too much grief, but it may be something an annotation generator (or
> creator) would want to attach to an annotation regardless of the location.
>
> Is this crazy or already possible? Events are closely tied to the
> annotation objects developers create in web applications with great effect,
> but to attach events/watchers to annotations in the wild may be a step too
> far.
>
> Patrick Cuba
> Center for Digital Humanities
> Saint Louis University
>



-- 
Rob Sanderson
Technology Collaboration Facilitator
Digital Library Systems and Services
Stanford, CA 94305
Received on Friday, 20 June 2014 19:24:36 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:22:06 UTC