RE: 🔔 Linked Data Notifications: Call for feedback and implementations

Hi all!



I’m at TPAC in a Social Web WG meeting, and I’d like to propose that our group give the Linked Data Notification specification some review/attention:

https://linkedresearch.org/ldn/




LDN is on the recommendation track within the Social Web WG, and it seems to suites many of our notification related use cases. It is likely that developers will consider this as an option for sending notifications about annotations stored in other annotation servers, perhaps as a system of relay among various Web Annotation Protocol servers, and even for receiving “sent” annotations from a browser when the necessary write-semantics within a Web Annotation Protocol server are not available.



Now that we have a bit more time as a working group I think a “first pass” review would help LDN make it through the recommendation track, and that we might also consider this for further mention in a “Notifications Note”—if we find some extra time somewhere before February. ;)



Issues may be filed at https://github.com/csarven/ldn/issues


Discussion here with regard to our specific use cases would be valuable to both this group and LDN.



Thanks, all!

Benjamin



--
http://bigbluehat.com/

http://linkedin.com/in/benjaminyoung




From: Sarven Capadisli<mailto:info@csarven.ca>
Sent: Monday, September 19, 2016 10:16 AM
To: Web Annotation<mailto:public-annotation@w3.org>
Subject: 🔔 Linked Data Notifications: Call for feedback and implementations



Hi all,

We're working on standardising a mechanism for discovering and
delivering notifications where the notification contents are in RDF. We
call it *Linked Data Notifications* (LDN) [1]. Catchy!

Notifications can be about anything: a personal message from a friend; a
pingback link; a comment on a blog post; a pointer to an annotation, an
invitation to collaborate; a calendar reminder, a changelog.

The spec is currently on the Rec-track in the W3C Social Web Working
Group, and we hope to take it to Candidate Recommendation at #TPAC2016.
We would benefit greatly from your review, if you are interested in such
a mechanism, and even better implementations of some part of the spec.
It can be a sender or consumer applications or a receiver (a server).

We wrote the spec around what already works in LDP, so if you have an
LDP server it already works as a receiver (just fill out an
implementation report). To advertise an Inbox where a resource can
receive notifications, all you have to do is e.g.:

<http://example.org/foo> ldp:inbox <http://example.net/inbox/> .

We'd love to hear from you if you're interested in trying out any part
of this, either personally or as part of a project. We'd also love for
you to fill in a receiver implementation report if you were involved
with an existing LDP implementation.

Issues are welcome on Github [2] and questions and comments on Gitter
[3], IRC [4] or the WG mailing list [5].

[1] https://www.w3.org/TR/ldn/

[2] https://github.com/csarven/ldn/issues

[3] https://gitter.im/csarven/ldn

[4] http://irc.w3.org/?channels=social

[5] public-socialweb@w3.org

-Sarven
http://csarven.ca/#i