Re: [Specifications] use manages block to advertise type of collection members

Reviewed 1 of 7 files at r1.
Review status: all files reviewed at latest revision, 3 unresolved discussions.

---

*[drafts/use-cases/1.1.security-considerations.md, line 18 at r2](https://reviewable.io:443/reviews/hydracg/specifications/132#-KrUSFWcxbytETQ1yIEc:-Kr_2TJ5W_aCIhX9duPe:bv2279w) ([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>

Since this PR proposes just one of possible solutions for the problem, I would like to suggest once again discussing and further clarifying the problem we try to address itself in https://github.com/HydraCG/Specifications/issues/126#issuecomment-322320409 
</blockquote></details>

@mlanthaler only clients written for a specific API will understand the contents of the given collection anyway. the will understand `hydra:Collection` and partial views. other than that I don't see how having the collection is really useful as fallback. won't this lead to

``` json
{
  "@id": "/some-person"
  "hydra:collection": [
    {
      "@id": "/some-person/friends"
    },
    {
      "@id": "/some-person/enemies"
    },
    {
      "@id": "/some-person/interests"
    }
  ]
}
```

how useful is it now? Also, this PR assumes that the content of a collection is inline. If you only got the target URL, the `hydra:collection` conveys completely no information.

---

*[drafts/use-cases/5.creating-new-event.md, line 29 at r1](https://reviewable.io:443/reviews/hydracg/specifications/132#-KrT4ZeUK43qWAnpOI76:-Kr_3pYuM-3ERYqQHOAI:bemgsjd) ([raw file](https://github.com/hydracg/specifications/blob/7a85c04e5cbfa0958d3ffd64bb3fafbb423a1361/drafts/use-cases/5.creating-new-event.md#L29)):*
<details><summary><i>Previously, lanthaler (Markus Lanthaler) wrote…</i></summary><blockquote>

[Nope](https://www.w3.org/TR/html5/links.html#rel-icon), unless I misunderstand you. It just describes in what relationship the target (the icon) stands to the context IRI (the document). The optional target attributes on a link are just hints that help a client to choose the supposedly best matching link. It must not trust them though but interpret what it actually gets when it dereferences the URL.
</blockquote></details>

Well, my point precisely (see the comment above). If the representation contained multiple `hydra:collection`links to multiple unrelated resources, the client would not be able to determine which one to dereference. Unless they are meant to be direct alternatives. Unless the `manages`-block will be mandatory...

---


*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-322415133 using your GitHub account

Received on Tuesday, 15 August 2017 08:49:49 UTC