- From: Tomasz Pluskiewicz via GitHub <sysbot+gh@w3.org>
- Date: Mon, 14 Aug 2017 17:25:51 +0000
- To: public-hydra-logs@w3.org
Reviewed 4 of 7 files at r1, 1 of 1 files at r2. Review status: all files reviewed at latest revision, 2 unresolved discussions. --- *[drafts/use-cases/1.1.security-considerations.md, line 18 at r2](https://reviewable.io:443/reviews/hydracg/specifications/132#-KrUSFWcxbytETQ1yIEc:-KrWjnr3sOtOBzyBPQqw:b-6whcbg) ([raw file](https://github.com/hydracg/specifications/blob/8c2db652e54f3e4ed52b855e05c73330d9d2d2ea/drafts/use-cases/1.1.security-considerations.md#L18)):* <details><summary><i>Previously, elf-pavlik (elf Pavlik) wrote…</i></summary><blockquote> Could you please explain what you mean by: > But, I don't like how it loses the API-scecificness. To my understanding clients need a way to discover from the `hydra:EntryPoint` collection with members of type `schema:Event`. But this general conversation already happens in https://github.com/HydraCG/Specifications/issues/126 </blockquote></details> What I mean is that replacing the API-specific term loses the link type between one resource (the Entrypoint) and the other (List of events). I think that the link relation trumps the manages block, so to speak. As for the client though, a way to discover collection of a given type may be useful. How would you like it to be based on `"@type": "hydra:Collection"` and the `manages`-block and not the predicate type? This way you can keep a more informative link predicate --- *[drafts/use-cases/5.creating-new-event.md, line 29 at r1](https://reviewable.io:443/reviews/hydracg/specifications/132#-KrT4ZeUK43qWAnpOI76:-KrWl6u74vFFICdRFAsm:b-1ow12t) ([raw file](https://github.com/hydracg/specifications/blob/7a85c04e5cbfa0958d3ffd64bb3fafbb423a1361/drafts/use-cases/5.creating-new-event.md#L29)):* <details><summary><i>Previously, elf-pavlik (elf Pavlik) wrote…</i></summary><blockquote> `@id` of the matching `hydra:Collection` I haven't thought of a case where multiple ones match but AFAIK `hydra:Link` also doesn't have restriction to reference only one resource </blockquote></details> Not really what I had in mind but you are right. I meant more of what I wrote in the other comment about losing the link type. In the end though I still don't entirely understand why you'd want a `getCollection` method instead of `getLink`. The former assumes what's on the other side. Not really hypermedia-y. --- *Comments from [Reviewable](https://reviewable.io:443/reviews/hydracg/specifications/132)* <!-- Sent from Reviewable.io --> -- GitHub Notification of comment by tpluscode Please view or discuss this issue at https://github.com/HydraCG/Specifications/pull/132#issuecomment-322253443 using your GitHub account
Received on Monday, 14 August 2017 17:25:54 UTC