Draft "Client-Side API for Annotations" #32
5 participants
gobengo
commented
May 13, 2015
|
@elf-pavlik I'm curious what you think about the DOMActivity straw man as well. |
|
I like the dom-activity proposal. Simple and flexible. |
|
+1. Would be great if @gobengo and @elf-pavlik could join one of the Annotation calls in the not-too-distant future to discuss? |
|
Pinging this issue to see if there's possible progress? Perhaps in coordination with SocialWeb? |
gobengo
commented
Nov 5, 2015
|
@azaroth42 I see this but don't have any progress to report. Looking back, I think my dom-activity writeup is too generic and vague to be realistically adopted any time within the Annotation WG charter timeline. |
akuckartz
commented
Nov 8, 2015
|
I would love to see an API which is not Annotation-specific. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Obviously the title of this issue is easier said than done. :)
Currently the farthest progress I've stumbled upon along this front is DOMAnnotations by @nickstenning, which is a great first start!
Continuing along a thought process I started in an ActivityPump issue, I'd like to probe to see if there's a single Web Interface we can standardize that can help with both this deliverable of Web Annotations as well as part of the Social API Deliverable of the Social WG.
Thus, I'd like to throw another contender into the ring, a DOMActivity API, where one use case is an ActivityEvent where
.activityis of the form "{actor} create {annotation}". Please annotate my straw man (for now) via GitHub Issues.