[annotator-dev] Branching v2.0.x
tilgovi at hypothes.is
Wed Oct 30 04:16:31 UTC 2013
First we would need to resolve the remaining differences between the
annotator model and the open annotation model.
Then JSON-LD can be added in various places at any time.
As you probably are aware, JSON-LD makes it possible to interpret JSON with
a linked data context. Last I checked, the framing abilities of JSON-LD
were insufficient to process annotator JSON into open annotation JSON-LD in
one step, due to the body and target resources being flattened into the
At this point, I'm convinced the model should change. For instance, it
disambiguates the meaning of tags on annotations. Right now I feel they're
ambiguous, referring either to comment or the target. If the tags were the
annotation body, rather than a field on the annotation, they would more
clearly apply to the target.
If we get the shape of the model right, contextualizing it with JSON-LD can
be done in plugins of various sorts, such as for a storage plugin that
interfaces with JSON-LD endpoints.
I think we may as well expose the context. Annotator code would just ignore
the context and continue using the friendly names for properties. But I'm
not sure it makes sense to add any processing weight to the annotator core
What do you think?
On Tue, Oct 29, 2013 at 7:09 PM, Ed Summers <ehs at pobox.com> wrote:
> Is it worthwhile considering JSON-LD and OpenAnnotation for v2.0? I
> know that OpenAnnotation is mentioned quite a bit w/r/t Hypothes.is
> and it seems like JSON-LD would possibly fit in fairly well with the
> On Tue, Oct 29, 2013 at 6:20 PM, Randall Leeds <tilgovi at hypothes.is>
> > In the interest of moving forward toward Annotator v2 I've just forked
> > current master branch to two branches: v1.2.x and v2.0.x.
> > I would like to propose that maintenance fixes only land on v1.2.x. We
> > should make a release there shortly with anything that's landed since the
> > last tag.
> > We should aim to land Nick's WIP branch on v2.0.x.
> > Kristof Csillag will follow up over the next few weeks with e-mails
> > proposing changes to v2.0.x that integrate work we've done at Hypothes.is
> > which may break backward compatibility.
> > In this way, we can continue to support the existing formats and
> > and make rapid changes to v2.0.x, stabilizing over time until we feel we
> > tag v2.0.0.
> > I wanted a way to start landing changes upstream without worrying about
> > v1.2.x compatibility. That way we don't have to land the WIP branch with
> > tons of other changes and call it v2.0.0 immediately. We can iterate to
> > v2.0.0 but things can be landed instead of staying on side branches
> > indefinitely.
> > Happy Annotating,
> > R
> > _______________________________________________
> > annotator-dev mailing list
> > annotator-dev at lists.okfn.org
> > http://lists.okfn.org/mailman/listinfo/annotator-dev
> > Unsubscribe: http://lists.okfn.org/mailman/options/annotator-dev
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the annotator-dev