22 Matching Annotations
  1. Aug 2023
  2. Jan 2023
    1. Example 2 HTTP/1.1 200 OK Content-Type: application/ld+json; profile="http://www.w3.org/ns/anno.jsonld" Link: <http://www.w3.org/ns/ldp#Resource>; rel="type" ETag: "_87e52ce126126" Allow: PUT,GET,OPTIONS,HEAD,DELETE,PATCH Vary: Accept Content-Length: 287 { "@context": "http://www.w3.org/ns/anno.jsonld", "id": "http://example.org/annotations/anno1", "type": "Annotation", "created": "2015-01-31T12:03:45Z", "body": { "type": "TextualBody", "value": "I like this page!" }, "target": "http://www.example.com/index.html" }
  3. Dec 2022
    1. This document is a companion to the IIIF Content Search API Specification, Version 2.0. It describes the changes to the API specification made in this major release, including ones that are backwards incompatible with version 1.0, the previous version.
  4. Nov 2022
    1. partnerships, networking, and revenue generation such as donations, memberships, pay what you want, and crowdfunding

      I have thought long about the same issue and beyond. The triple (wiki, Hypothesis, donations) could be a working way to search for OER, form a social group processing them, and optionally support the creators.

      I imagine that as follows: a person wants to learn about X. They can head to the wiki site about X and look into its Hypothesis annotations, where relevant OER with their preferred donation method can be linked. Also, study groups interested in the respective resource or topic can list virtual or live meetups there. The date of the meetups could be listed in a format that Hypothesis could search and display on a calendar.

      Wiki is integral as it categorizes knowledge, is comprehensive, and strives to address biases. Hypothesis stitches websites together for the benefit of the site owners and the collective wisdom that emerges from the discussions. Donations support the creators so they can dedicate their time to creating high-quality resources.

      Main inspirations:

      Deschooling Society - Learning Webs

      Building the Global Knowledge Graph

      Schoolhouse calendar

  5. May 2022
  6. Mar 2022
    1. but they would have to find it for it to be of any use to them, and this is something I only have so much energy to advertise.

      This is where widespread awareness of annotations would be useful. A service like Hypothes.is inherently functions as a sort of hub for relaying gossip about a given resource.

  7. Jan 2022
  8. Oct 2021
    1. social annotation

      Had I known about Hypothesis at the time of my collaboration with Ilaria Forte, I likely would have suggested this as a tool for documenting the stream of consciousness, collecting stories in the context of the media that people are experiencing on the web.

    1. Private links One must be able to add one's own private links to and from public information. One must also be able to annotate links, as well as nodes, privately.
  9. Jun 2021
    1. But here's the twist. That edit window is wired to your personal cloud. That's where your words land. Then you syndicate your words back to the site you're posting to.

      This is more or less how linked data notifications work. (And Solid, of course, goes beyond that.)

    2. If they did I think there would actually be some quality of discussion, and it might be useful

      I used to think this. (That isn't to say I've changed my mind. I'm just not convinced one way or the other.)

      Another foreseeable outcome, relative to the time when the friend here was making the comment, is that it would lead to people being nastier in real life. Whether that's true or not (and I think that it might be), Twitter has turned out to be a cesspool, and it has shown us that people are willing to engage in all sorts of nastiness under their real name.

  10. May 2021
    1. So she writes an explanatory note for Jack, links the note to the Parallel Compiling report, and then links the note to Jack's mailbox: in this open hypertext system, a mailbox is simply a publicly readable document to which the owner has attached a sensor.

      Okay, so this is back to looking like LDN, except the (novel?) idea that after sending the annotation to the annotation service responsible for annotations to the report, her final annotation gets sent to that that annotation service corresponding to a different document—Jack's mailbox. Interesting!

      (Maybe this is explicitly laid out as a possibility in one of the several pieces associated with LDN and I just never noticed?)

    2. a hypermedia server might use sensors to alert users to the arrival of new material: if a sensor were attached to a document, running a new link to the document would set off the sensor

      Linked data notifications?

      (I like the "sensor" imagery.)

  11. Jan 2021
  12. Aug 2020
  13. Oct 2018
  14. Sep 2018
    1. code for transforming Annotator JSON into Web Annotation's JSON-LD with the most minimal, unsmart means (read: doesn't understand graphs) sort of way possible.
  15. Nov 2017
    1. Back in 1993, when Eric Bina and I were first building Mosaic, it seemed obvious to us that users would want to annotate all text on the web – our idea was that each web page would be a launchpad for insight and debate about its own contents. So we built a feature called "group annotations" right into the browser – and it worked great – all users could comment on any page and discussions quickly ensued. Unfortunately, our implementation at that time required a server to host all the annotations, and we didn't have the time to properly build that server, which would obviously have had to scale to enormous size. And so we dropped the entire feature.
  16. Jan 2014
    1. The process of tying two items together is the important thing.

      Annotations are at the Web’s core.