h

> Does Hypothes.is have a self-hosting option? https://web.hypothes.is/sales/ The code for both the client and server are open source (https://github.com/hypothesis/h) so this is possible. The server is designed to support the needs of large scale deployments, so this does come with some complexity compared to a system you would design for smaller scale usage. The text on https://web.hypothes.is/ mostly targets schools and universities, because Hypothesis pays for itself by selling integrations with online learning platforms (Canvas, D2L, Blackboard etc.) and associated support.

> Though nowhere is it shown that clinicians are even competent enough to add RDFa linked data annotations to their TXT unstructured notes with an encabulator. You can add Linked Data (JSON-LD RDF) annotations with threaded markdown to document Trump vectors with W3C Web Annotations. This [SNMOED-CT, ICD10-] competition could be scored with Web Annotations as the schema for the output. W3C Web Annotations open source implementations: - hypothesis/h: https://github.com/hypothesis/h - https://github.com/linkeddata/dokieli - https://www.w3.org/annotation/wiki/Implementations

https://github.com/hypothesis/h https://github.com/hypothesis/client

Hypothesis/h is a (Pyramid) web app with a JS widget that can be added to the HTML of a page manually or by the Hypothesis browser extension, which enables you to also comment on PDFs, WAVs, GIFs: https://github.com/hypothesis/h From the W3C Web Annotation spec that Hypothesis implements https://www.w3.org/TR/annotation-model/ : > Selectors: Fragment Selector, CSS Selector, XPath Selector, Text Quote Selector, Text Position Selector, Data Position Selector, SVG Selector, Range Selector, Refinement of Selection > States: Time State, Request Header State, Refinement of State

A sibling comment points out that it seems to be implemented here: https://github.com/hypothesis/h/blob/master/h/presenters/ann... Or is this something different from what you have in mind?

Both the frontend and server seem to be open source. https://github.com/hypothesis/h https://github.com/hypothesis/client

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 t

Slightly on a tangent, but https://github.com/hypothesis/h/issues/777 could be a good target for https://solidproject.org/ to address. The Web Annotation Vocabulary is defined in RDF, so there should be zero overhead.

I tried them a while ago. Really liked it but put it aside till they implement https://www.w3.org/annotation/ as promised. Just checked https://h.readthedocs.io/en/latest/api/ and the v2 API in development has nothing to do with the W3C standard. UPD: there is not a single issue open on the main repo wrt W3C standard implementation: https://github.com/hypothesis/h/issues?q=is%3Aissue+is%3Aope.... The post I took as a promise: https://web.hypothes.is/blog/annotation-is-now-a-web-standar...

You guys should check out https://test.hypothes.is. Non profit open source project that does this for the entire web. Here's the github: https://github.com/hypothesis/h Randall, the lead developer, is one of the authors of the open annotation spec: http://www.openannotation.org Dan, the founder, recently put together the I Annotate conference, which brought together all the individuals and groups who have been applying annotation to their problem domains for the past few years. I designed the interface. Annotation should be open source, standardized, and portable, not locked into little silos. Also, I'm not pg, but if I was, I would find this a bit... odd.