- From: elf Pavlik via GitHub <sysbot+gh@w3.org>
- Date: Sat, 04 Nov 2017 01:14:23 +0000
- To: public-hydra-logs@w3.org
So the only difference seems that with `hydra:memberTemplate` we have an instance of `hydra:TemplatedLink` (just like `hydra:search`) with clearly defined meaning, while with something like bespoke `api:member` clients which don't implement that additional `api:` vocab (eg. plain Heracles.ts) would just understand that they have an instance of `hydra:TemplatedLink` but not know anything about its meaning, rendering it something similar to `rdfs:seeAlso`. At the same time, I agree that client pseudo code introduced in #143 seems to start with assumption that it has to look for `hydra:TemplatedLink` so that code would fail if service choses to add members by having `operation` - `schema:CreateAction` with `POST` directly on the collection. As we discussed during the call, we should not assume that we already found a solution to the challenge. I see it more as stil exploring certain possibility which we may still find not an appropriate approach. -- GitHub Notification of comment by elf-pavlik Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/16#issuecomment-341861321 using your GitHub account
Received on Saturday, 4 November 2017 01:14:27 UTC