- From: Markus Lanthaler <markus.lanthaler@gmx.net>
- Date: Sun, 29 Apr 2018 19:14:16 +0200
- To: "'Mark Wilkinson UPM'" <mark.wilkinson@upm.es>, "'Lorenzo Moriondo'" <tunedconsulting@gmail.com>
- Cc: "'Hydra'" <public-hydra@w3.org>
On 27 Apr 2018 at 11:58, Mark Wilkinson UPM wrote: > Well, it helps in that it seems to confirm that I cannot use message > schema definitions outside of what Hydra allows... :-) > > On 04/27/2018 11:54 AM, Lorenzo Moriondo wrote: >> Hi, >> >> As per the definition of `hydra:expects`: its domain is a type >> `hydra:Operation` and its range is a type `hydra:Class`. >> >> https://github.com/lanthaler/Hydra/blob/master/spec/latest/core/core.jsonld#L256 >> >> So it is that it is not possible to use these properties to reference >> entities that are not Hydra classes or its subclasses. >> Hope this helps. Please note that that isn't how RDFS is defined. What range/domain says it that the resources in subject/object position are of those types. They don't describe what types are allowed. SHACL is definitely better suited for the latter -- Markus Lanthaler @markuslanthaler
Received on Sunday, 29 April 2018 17:14:55 UTC