- From: elf Pavlik via GitHub <sysbot+gh@w3.org>
- Date: Sun, 08 Oct 2017 16:22:00 +0000
- To: public-hydra-logs@w3.org
> But whether it will do a PUT or POST or a LINK request is discovered at runtime and can change over time... If we continue with the *liking a video* example. * POST would happen on resource representing collection (`/users/elfpavlik/likes`) * PUT would happen on a resource which doesn't event exist #141 and client would need a URI Template * LINK would happen on `/users/elfpavlik` (with `rel`) and/or `/videos/144522067` (with `rev`) But in all cases above IMO client needs a way to *follow its nose* from `/videos/144522067` and only rely on understanding Hydra plus `sor:likes` (or some other property in other similar use cases) Personally I would prefer some kind of generic `foo:Link` and `foo:Unlink` actions which would specify any instance of `rdf:Property` (or its reverse) rather than tying to define action type for any possible property. -- GitHub Notification of comment by elf-pavlik Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/134#issuecomment-335017889 using your GitHub account
Received on Sunday, 8 October 2017 16:21:49 UTC