- From: elf Pavlik via GitHub <sysbot+gh@w3.org>
- Date: Sat, 21 Oct 2017 00:52:29 +0000
- To: public-hydra-logs@w3.org
continuing from: https://github.com/HydraCG/Specifications/issues/141#issuecomment-336729288 >> @elf-pavlik: since `hydra:Operation` doesn't provide a way to specify `hydra:IriTemplate` it seems that we may not use `schema:CreateAction` with both HTTP POST and HTTP PUT > @lanthaler: I realize it is not properly documented but the intention was always that operations would work on IriTemplates` just as they work on resources... Does it mean that if we start from an instance of `hydra:Operation` and follow `hydra:operation` in reverse direction, then 1) if we get an instance of `hydra:Resource` we use IRI that denotes that resource (JSON-LD `@id`) 2) if we get an instance of `hydra:IriTemplate`, we ignore IRI that denotes that template (JSON-LD `@id`) and instead use IRI based on `hydra:template` and `hydra:mapping` > @lanthaler: otherwise things like hydra:search wouldn't work. Looking at example of `hydra:search` http://www.hydra-cg.com/spec/latest/triple-pattern-fragments/#controls I don't see `hydra:Operation` or `hydra:operation` used there at all. I see `hydra:search` relating an instance of `hydra:Resource` directly to an instance of `hydra:IriTemplate`. -- GitHub Notification of comment by elf-pavlik Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/3#issuecomment-338352533 using your GitHub account
Received on Saturday, 21 October 2017 00:52:32 UTC