Yes we are in close contact with the Hypothes.is team and may develop some shared components in the future. We already use their anchoring library.
Internally we don't store the annotations in W3C standard yet, but will provide that as soon as we get to develop the ability to export or access annotations via an API.
How do you imagine Memex being used as a backend in your context?
Once we offer more integrations to other services, it is definitely thinkable to also make annotations from Hypothes.is searchable. Is that something along the lines you're thinking of?
Internal representation doesn't matter to me as much as the external view, so I guess I'm actually looking for your planned extensible API - I'll be eagerly awaiting that.
With more and more annotation services, there may come a need for an "annotation manager". Memex could be the manager for Hypothes.is as you suggest, but a separate manager could also use Memex and Hypothes.is as backends. So, for example, the annotation act is done with Memex, but the research stage is done with a separate tool.
Cool product/vision! I like your guys' stance on the user's data and with an API might settle on this one. :)
Oli here from the WorldBrain.io team
Yes we are in close contact with the Hypothes.is team and may develop some shared components in the future. We already use their anchoring library.
Internally we don't store the annotations in W3C standard yet, but will provide that as soon as we get to develop the ability to export or access annotations via an API.
How do you imagine Memex being used as a backend in your context? Once we offer more integrations to other services, it is definitely thinkable to also make annotations from Hypothes.is searchable. Is that something along the lines you're thinking of?
Cheers! Oli