- From: Karol Szczepański <karol.szczepanski@gmail.com>
- Date: Sat, 18 Jun 2016 21:04:38 +0200
- To: <public-hydra@w3.org>, "Tomasz Pluskiewicz" <tomasz@t-code.pl>
Tom, Dietrich >First the term "to POST to the API" is misleading. What you are doing is >posting representation to a resource. After all, what is the API? Also >"path of predicates" is too RDF-centric. Could we just call them links? > >How about instead we phrase such interactions like below? The example could >be from a collection resource. > >1. As a client, I want to follow the Link relation 'next' of my resource >representation (this would naturally mean a GET with HTTP) > >2. As a client, I want to invoke the operation 'AddElement' (this would >mean whatever the Hydra documentation+representation defines) I'd also stick to high-level operations/links. These are more bound to given domain - HTTP is just a tool here. I'd give up on making a distinction between link and operation, but I'd lean to operations rather than to links. I acknowledge links as specific operations where you don't need a request body. Best Karol
Received on Saturday, 18 June 2016 19:02:34 UTC