My PhD work would not have been possible without Hypothes.is. My group uses it for a variety of information extraction and curation tasks, and I'm fairly certai

My PhD work would not have been possible without Hypothes.is. My group uses it for a variety of information extraction and curation tasks, and I'm fairly certain that one of my colleagues has the highest number of human made annotations in the system (though in private groups). Hypothes.is is great for prototyping curation workflows to explore what is possible before spending time implementing yet another tool. It also hits the sweet spot for having a UI that is just accessible enough for non-technical users that can display annotations made by bots. We have been using hypothes.is as the backend to crawl [0] research resource identifiers from the scientific literature for 4 years, and it has been solid the whole time. I see some questions/concerns about the w3c compliance of the API. I'm pretty sure that there is just a switch the needs to be flipped, and that it has been implemented. Yep, it has [1]. Also as others have suggested it is fairly straight forward to set up your own annotation store, though it is not simple to replicate the Hypothes.is setup. I hope that the pivot to education continues to go well so that it can fund the infrastructure, because Hypothes.is provides a very valuable (if hard to capture the value of) service. 0. https://github.com/SciCrunch/scibot https://github.com/SciCrunch/scibot 1. https://github.com/hypothesis/h/blob/master/h/presenters/annotation_jsonld.py https://github.com/hypothesis/h/blob/master/h/presenters/ann...