- From: Tomasz Pluskiewicz <tomasz@t-code.pl>
- Date: Mon, 14 Mar 2016 11:28:11 +0000
- To: "Karol Szczepański" <karol.szczepanski@gmail.com>, "Asbjørn Ulsberg" <asbjorn@ulsberg.no>
- Cc: public-hydra@w3.org
Guys, I'm glad you responded but your replies were sort of beside the point :) > - PUT /blog/published/whatever > That's what I was thinking. The client the blog post in the last request. How do we describe that with Hydra. As an operation or as a link? I think that Hydra is missing an important piece here. We can define operations on self, and linking to other resource but it should be possible to describe operations on linked resources. And I don't mean supportedClass/supportedProperty/supportedOperation path. This is still operation on self, but the self is the linked resource. What I mean is, given resource /a, with a link to /x, I want the client to send the representation(/a) to that resource /x: POST /x HTTP/1.1 representation(/a) In the blog example that would be more like PUT /blog/published/whatever HTTP/1.1 representation(/blog/whatever)
Received on Monday, 14 March 2016 11:28:58 UTC