- From: Ruben Verborgh <ruben.verborgh@ugent.be>
- Date: Mon, 21 Apr 2014 10:19:20 +0200
- To: Thomas Hoppe <thomas.hoppe@n-fuse.de>
- Cc: public-hydra@w3.org
Hi Thomas, > I want againt stress that existence of such an operation > is required if you want to integrate the hydra based API > description with a solution to define authorization constraints (who can read what in an API?). That's not true; “RetrieveResourceOperation” is not the only possible solution for authorization. What I propose is that you create an issue "authorization for read requests" and that we have a look at different options. I don't think it makes sense to accept RetrieveResourceOperation just because it is one solution to another problem. > I also don't understand why only resource modification is in focus of > hydra as you say - considering collection searching, filtering and paging this > is not true. They are in Hydra scope, but they are different things. Reading stuff is changing application state, writing stuff is changing resource state. See ISSUE-44. Best, Ruben
Received on Monday, 21 April 2014 08:19:55 UTC