- From: Ruben Verborgh <ruben.verborgh@ugent.be>
- Date: Wed, 23 Apr 2014 09:25:07 +0200
- To: Thomas Hoppe <thomas.hoppe@n-fuse.de>
- Cc: public-hydra@w3.org
Hi Thomas, > Seeing hydra as a vocabulary to describe APIs it is just annoying to have 3 of four basic REST > operations and one is missing. There is no such thing as "four basic REST operations"; hence, there is no structural reason for Hydra to have four. The REST architectural style distinguishes between application state, which is kept on the client, and resource state, which is kept on the server. When you just retrieve representations of resources, you only change the application state, not the resource state. At the moment, Hydra operations capture actions on the resource state, which is why there are no operations for reading. > The authorization concern is not only for read requests. Exactly. It's a cross-cutting concern, so there is no need to solve it in operations. > I will share my solution for this to the list once it is somewhat presentable anyway. Great, looking forward to that. Best, Ruben
Received on Wednesday, 23 April 2014 07:26:38 UTC