Doesn't support Open Annotation

[azaroth42]

For code in the Open Annotation github account, it doesn't support the Open Annotation model. It should.

[tilgovi]

Would be better if opened on openannotation/annotator-store, IMO.

Annotator itself doesn't particularly care about the API protocol. It may well make sense to use an Open Annotation data model in memory client side but that's all pretty opaque. It's not really clear what it means for Annotator itself to "support" any particular data model.

Should we publish a module which implements a REST-ish API using some semantic serialization conforming to Open Annotation spec in this organization? Absolutely. Is it in this repo? Not clear.

We also haven't, as a community, defined any APIs for interop yet, though common patterns used all over the place would be simple enough for many uses (GET/PUT/DELETE to annotation resources or their collections by specifying the id in the body or query string, POST to the collection to create a new one with an automatic id).

[azaroth42]

annotator-store should, for sure. But equally, the client should be able to consume, process and render annotations serialized in the Open Anno data model. Then when we encounter a new store implementation that exposes annotations using the model, it should be trivial to extract them from whatever wrapping they're contained in. And before long, with any luck, that wrapper will be standardized too. If that shouldn't be here, then please move to where it should be :)

Using it internally ... if it makes sense great. If not, no problem.

A REST(-ish) API would be great, and indeed there's common patterns to follow. Anyone coming to the problem would likely just reinvent the annotator store API. I expect that this will be standardized as-is, or with minimal changes, beyond the serialization of the individual annotations.

[nickstenning]

For the avoidance of doubt, I'm totally in favour of either

1. a store plugin that speaks OA-compatible JSON-LD, or
2. an option to the existing store plugin that allows it to speak OA-compatible JSON-LD

It hasn't happened simply because I haven't had time yet. If anyone watching this repo has such a thing or wants to work on such a thing: we'd merge this!

[BigBlueHat]

@Treora showed me a demo on Friday of some annotator-store work underway that provides the JSON-LD @context goodness to the individual annotations (so far).

The flip side may take a bit more time (JSON-LD / RDFa JS library research, etc), but is certainly something to consider! Oh, the possibilities. 😉

[nickstenning]

From this point forward, I'm going to be keeping the Annotator issue tracker for bug reports only. Enhancements and feature requests should be made on the mailing list.

As this is a feature request, I'm going to close this issue. If you feel that I've miscategorised the discussion, and there is a genuine unaddressed bug, feel free to reopen with an explanation.

[tilgovi]

Ooh.

So this one is one I'm voting to keep open. We've moved this repo to the openannotation organization and the working group has officially started so I think it's rather important we tackle this one.

[azaroth42]

+1 that it's a bug in the current context of openannotation, not a feature request. Also, a bug that will hopefully be closed in October given the Stanford/Hypothes.is/Harvard joint sprint.

[leinfelder]

+1. October? Great!

[tilgovi]

I'm going to be putting some examples of anchoring using OA selectors in the next week or two.