Socialwg/Social API/Candidates

One good use case for applying these is SWAT0.

See also: Socialwg/Social API patterns

There are a few different candidate APIs:

Accepted Candidates

At the Socialwg/2015-03-17 f2f meeting the WG resolved on only the following three candidates as explicitly accepted for consideration for development of a Social Web WG Social API. All others are dropped.

Other candidates may be considered if someone in the working group is able to provide a live demo of them of one or more User Stories.

Micropub

https://indiewebcamp.com/Micropub

Micropub implementations

• 12+ different client implementations deployed across multiple real world sites (see link for specific citations) that interoperate with
• 8+ different server implementations deployed across multiple real world sites (see link for specific citations)

Micropub notes

• write only, since reads occur directly via HTTP request of URLs to HTML pages
• currently uses widely supported application/x-www-form-urlencoded

IndieAuth

https://indieauth.com/ - in so far as it was used as part of Micropub

HTTP GET microformats

HTTP GET microformats for read, in so far as it was used as part of and complementary with Micropub

Micropub Questions Answers

• How does it handle nested resources? (eg. JSON-LD embedding)
  • Using https://indiewebcamp.com/Micropub#Nested_Microformat_Objects

• What standard data formats does it use? [1], just form-urlencoded key, value pairs with few examples on its wiki page — Pavlik elf (talk) 23:16, 5 March 2015 (UTC)
  • form-encoded is standard
  • key / value pairs are standard from various microformats vocabularies such as h-entry Tantek Çelik (talk) 21:10, 13 March 2015 (UTC)

ActivityPump

A derivative of pump.io. See documentation.

See also: https://github.com/e14n/pump.io/wiki/Clients

LDP / SoLiD

The LDP spec can be thought of as a successor to WebDAV and Atom Protocol, as a way to turn the web into a Read-Write platform. It is simpler and more extensible than WebDAV due to its building on the unifying Semantic Web stack. It is more general that the Atom Protocol as it can build on the extensibility that comes with RDF. In either case it is designed as both of them to be general enough to be useful to any application ( see the Linked Data Protocol Primer and use cases).

SoLiD is a specific proposal for how to use LDP to address the User Stories. See https://github.com/linkeddata/SoLiD

For an overview that highlights the Social Web features of LDP see Shorter description of LDP APIs presented on Social Web Working Group teleconf December 16, 2014. There are 10 known tested implementations of LDP as of January 2015.

Dropped Candidates

Apache UserGrid API

http://usergrid.readthedocs.org/en/latest/concepts/activity.html

Hydra

http://hydra-cg.com

• http://www.hydra-cg.com/spec/latest/core/

Linked Data Fragments

http://linkeddatafragments.org

LDF implementations

• client: http://client.linkeddatafragments.org/
• server: http://linkeddatafragments.org/software/ also powers http://fragments.dbpedia.org/

{json:api}

http://jsonapi.org/

json api implementations

http://jsonapi.org/examples/

• client
  • ember-data
  • backbone-jsonapi
  • orbit.js
  • jsonapi-ios
• server
  • over 15 implementations

Open Social Activity Streams API

http://www.w3.org/Submission/2014/SUBM-osapi-20140314/

Not considered as candidates

remoteStorage

http://remotestorage.io

SocketHub

http://sockethub.org

BuddyCloud

http://buddycloud.com

See also

• http://martinfowler.com/articles/richardsonMaturityModel.html
• Sam Goto
  • http://blog.sgo.to/2014/02/the-w-stands-for-web.html
  • http://blog.sgo.to/2014/02/the-gaps-in-resource-oriented-architectures.html
  • http://blog.sgo.to/2014/02/a-proposal-for-schema-org-actions.html
  • http://blog.sgo.to/2014/02/rows.html
  • http://blog.sgo.to/2014/03/rows-and-idls.html