- From: Thomas Hoppe <thomas.hoppe@n-fuse.de>
- Date: Sun, 20 Apr 2014 09:30:43 +0200
- To: public-hydra@w3.org
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?). At least without introducing a new operation. 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.
Received on Sunday, 20 April 2014 07:31:20 UTC