W3C home > Mailing lists > Public > public-rww@w3.org > October 2012

Re: Activity Pingback

From: Sandeep Shetty <sandeep.shetty@gmail.com>
Date: Tue, 2 Oct 2012 00:52:26 +0530
Message-ID: <CACO=zvp38K4EoSVp2kaAN-_zqGmNhyDf6tapTMK-k06w7NucDg@mail.gmail.com>
To: Henry Story <henry.story@bblfish.net>
Cc: public-rww@w3.org
Hey Henry,

> How does it compare in your view to the pingback protocol we detailed
> here?
>
> http://bblfish.net/tmp/2011/05/09/

RESTful Pings is well thought out, espcially the HTML form and
webID/Oauth based authentication bits
(http://www.w3.org/community/rww/wiki/File:Client-Side_Pingback.png).

One of my main goals with Activity Pingback, is developer experience
(DX) and keeping things as simple as possible (for implementors) with
a minimum surface area of concepts and options while being ready to be
implemented/deployed as of yesterday. Activity Pingback also tries to
retain familiarity with Pingback/Trackback for existing developers.

The larger project that I'm working on (http://activityweb.org/)
borrows heavily from blogging and doesn't treat things like users in a
special way. Any URI addressable resource can be "followed" and
notified of activities related to it. Within that context, Activity
Pingback is singularly focused on sending activity related
notifications (in the form of JSON Activity Streams) to any URI
addressable resource with a good enough way to verify that the
notification originated from the said resource.

-- 
Sandeep Shetty
Founder, Simpthings
http://simpthings.com/
http://sandeep.shetty.in/p/about.html
Received on Monday, 1 October 2012 19:23:16 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 1 October 2012 19:23:16 GMT