- From: John Walker <john.walker@semaku.com>
- Date: Tue, 20 Jan 2015 08:14:26 +0100
- To: ☮ elf Pavlik ☮ <perpetual-tripper@wwelves.org>
- Cc: Ruben Verborgh <ruben.verborgh@ugent.be>, Hydra <public-hydra@w3.org>
See here: http://en.m.wikipedia.org/wiki/Dereferenceable_Uniform_Resource_Identifier Although one could argue that schema identified with HTTP URI are often dereferenceable but are intended to be cached (perhaps indefinitely) on the client. Regards, John On 20 Jan 2015, at 00:18, ☮ elf Pavlik ☮<perpetual-tripper@wwelves.org> wrote: > On 01/19/2015 01:05 PM, Ruben Verborgh wrote: >> Dear all, >> >> In a previous thread [1], the following issue came up: >> How can a server suggest to a client that a certain resource can/should be dereferenced? >> >> I created Issue 91 to track this: https://github.com/HydraCG/Specifications/issues/91 >> >> Currently proposed solutions are: >> >> - Solution 1: set the type of the resource to hydra:Resource >> https://github.com/HydraCG/Specifications/issues/91#issuecomment-70482488 >> >> - Solution 2: set the hydra:dereferenceable property >> https://github.com/HydraCG/Specifications/issues/91#issuecomment-70482696 > > Could someone please provide an example use case for http(s) IRIs not > intended as dereferenceable? > >
Received on Tuesday, 20 January 2015 07:14:58 UTC