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

interesting!

i'd like to add 2 cents from a slighty different angle which are still
related: actual creation of such notifications using the rdf-language at
scale as a constant stream of changesets, (e.g. http://vocab.org/changeset/).
this can be done by running an apache kafka [1] cluster producing simple
turtle messages. for demonstration purposes for the bigdata-europe project
[2] we've created an rdf4j sail implementation, which produces lists of
additions and deletions as kafka messages. these are regularly received by
any running instance of said sail implementation.  see here [3] for a
docker version of the experiment that can run on marathon.

krj

[1] https://kafka.apache.org/
[2] https://www.big-data-europe.eu/
[3] https://github.com/big-data-europe/docker-kafkasail


*Jürgen Jakobitsch*
Innovation Director
Semantic Web Company GmbH
EU: +43-1-4021235-0
Mobile: +43-676-6212710
http://www.semantic-web.at
http://www.poolparty.biz


PERSONAL INFORMATION
| web       : http://www.turnguard.com
| foaf      : http://www.turnguard.com/turnguard
| g+        : https://plus.google.com/111233759991616358206/posts
| skype     : jakobitsch-punkt
| xmlns:tg  = "http://www.turnguard.com/turnguard#"

2016-09-18 15:07 GMT+02:00 Sarven Capadisli <info@csarven.ca>:

> 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
>
>