- From: Karol Szczepański <karol.szczepanski@gmail.com>
- Date: Sat, 31 Oct 2015 13:53:22 +0100
- To: <public-hydra@w3.org>, "Dietrich Schulten" <ds@escalon.de>
Hi Dietrich
Just to deliberate a little bit with you...
>> Well, first of all - not all variables needs to be replaced. Consider
>> query string parameters - these are usually optional
>what makes you think so?
>hydra:next </gadgets?page=4>
>;-)
Well, call to /gadgets is as valid as the one with ?page=4. Indeed server
may decide to either return 404, some 3XX or whatever other status, but it's
the /gadgets makes the server to pickup a request.
>> Other thing is when a variable sits in the path.
>A path variable is not a required variable in UriTemplate, rather when
>there is a path variable and its value is empty or undefined, you get
>different expansions:
>empty=""
>undef=null
> /foo{/empty}/bar /foo//bar
> /foo{/undef}/bar /foo/bar
>A service would have to make them required in the hydra description of
>the variable mapping if it thinks the value must be present. Otherwise
>the UriTemplate expansion happily feasts on your undefined path segment
>variable ;-P
Agreed
Best,
Karol
Received on Saturday, 31 October 2015 12:53:52 UTC