- From: ☮ elf Pavlik ☮ <perpetual-tripper@wwelves.org>
- Date: Tue, 04 Nov 2014 21:30:32 +0100
- To: Markus Lanthaler <markus.lanthaler@gmx.net>, public-socialweb@w3.org
On 11/04/2014 09:22 PM, Markus Lanthaler wrote: > On 3 Nov 2014 at 19:17, ☮ elf Pavlik ☮ wrote: >> On 11/03/2014 06:50 PM, James M Snell wrote: >>> Yes we do. as:Link serves two purposes: >>> >>> 1. As a marker class used to indicate that the @id can be dereferenced; and >> >> Sounds like exactly the same aim as hydra:Link >> http://www.hydra-cg.com/spec/latest/core/#adding-affordances-to-represent >> ations > > Yep, AFAICT as:Link is the same as hydra:Resource (not hydra:Link which is for properties whose values are dereferenceable resources... as:preview would be a hydra:Link if it's value is always a dereferenceable resource). I would really like that we can simply reference Hydra Core as mechanism which also addresses current direction as:Link takes. Markus can we find somewhere more information about requirement related to need of caution not to merge Hydra API Documenation with the data it provides?
Received on Tuesday, 4 November 2014 20:32:51 UTC