- From: elf Pavlik <perpetual-tripper@wwelves.org>
- Date: Mon, 07 Dec 2015 00:10:22 +0100
- To: Evan Prodromou <evan@e14n.com>
- CC: public-socialweb@w3.org
Hi Even, On 12/06/2015 11:13 PM, Evan Prodromou wrote: > ActivityPump is restful. That's the whole point. I will very likely also mention it but I see it more as RPC than REST. For example to add someone to the list of people I follow one doesn't do HTTP PATCH to modify that list. Similar with 'favorites' collection. On the other hand it uses HTTP GET, PUT, DELETE to update particular activities. I will try to read current draft again, but I don't think it explains how to deal with objects other than activities. For example collections of objects with type schema:Demand having relation with the actor through property schema:seeks. While modifying collection of followers/followings and favorites, just links to existing resources which someone else have published. To create new schema:Demand or schema:Offer, many people using REST would expect to use HTTP POST to the relevant collection. IMO ActivityPump has some elements of REST, but I would stay careful with calling it RESTful. Cheers! > > On Dec 6, 2015 11:31 AM, elf Pavlik <perpetual-tripper@wwelves.org> wrote: >> >> Hello, >> >> On Tuesday I will give talk at http://paris.apidays.io/ about 'API >> standardization work in W3C groups'. Since this talk belong to REST >> track, I will quickly introduce Linked Data Platrorm & SoLiD, Hydra & >> Link Data Fragments and possibly Schema.org Action. In Social WG only >> AS2.0 Action Handlers seem to have intention to support REST. I still >> see it listed as Editor's Draft on WG wiki but not any more in github >> repository. I will probably mention them on my slides either way and >> just explain their status based on eventual reply to this email. >> >> Thanks!
Received on Sunday, 6 December 2015 23:10:33 UTC