Closed alien-mcl closed 4 years ago
I've replaced approach in this PR with last commit. This is due to potential issue raised by @angelo-v on one of the occasions. Previous approach sub-classed hydra:TemplatedLink
from hydra:Link
. While convenient, it could cause issues with interpretations of the resource on the right side of the relation.
It could be considered a link, while it shouldn't - it will be an IRI template that needs to be resolved first (becoming a real link).
New approach feels safer from that point of view still providing required semantics.
Summary
The
hydra:TemplatedLink
is not formally considered ahydra:Link
so it cannot formally have any of the properties that are allowed forhydra:Link
. While in RDF each property can be used on every resource, it is still preferred to explicitly define some of the relations between terms so the client implementation is easier and the data model is stable.More details
The
hydra:TemplatedLink
is sub-classed fromhydra:Link
in this template making it formally also ahydra:Link
which enables it to all properties define forhydra:Link
with eitherrdfs:domain
orschema:domainIncludes
.