- From: Markus Lanthaler <markus.lanthaler@gmx.net>
- Date: Fri, 13 Mar 2015 18:44:09 +0100
- To: <public-hydra@w3.org>
On Wednesday, March 11, 2015 5:24 PM, Nandana Mihindukulasooriya wrote: > On Sun, Mar 8, 2015 at 1:25 PM, Dietrich Schulten wrote: >> Am 06.03.2015 um 17:45 schrieb Nandana Mihindukulasooriya: >>> Trying to go even a bit more further, I was wondering whether there was >>> a way to describe the information about the expected or supported >>> headers. For example, If I want to tell a client that it can send a Slug >>> header [1] or a Prefer header for a particular supported operation, is >>> it possible with Hydra? >> >> There is no way to specify supported request headers in hydra yet. On >> the other hand, since the client is an LDP client which handles LDP >> containers, it should know about Slug and Prefer header params and their >> possible effects anyway :) > > Thanks a lot for the reply. > > Yes, that's true. At the moment, the main advantage of using hydra > with LDP is the fact that it makes it possible to describe the > expected content for each operation (without using a custom media > type) which is not possible with LDP until the RDF Data Shapes WG > comes with a proper solution. However, being able to describe about > headers is useful too. For example, the slug header is a MAY and some > servers may support it while others may not. At the moment, there is > no way to find it out without trial and error. This seems like a reasonable enhancement to me. I'm offline at the moment. Could you please file an issue in case I forget to do it when I'm online again? Thanks, Markus -- Markus Lanthaler @markuslanthaler
Received on Friday, 13 March 2015 17:44:52 UTC