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

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:-KrWvvCnjeEYb2_wB-YC:blormog) ([raw file](https://github.com/hydracg/specifications/blob/8c2db652e54f3e4ed52b855e05c73330d9d2d2ea/drafts/use-cases/1.1.security-considerations.md#L18)):*
<details><summary><i>Previously, lanthaler (Markus Lanthaler) wrote…</i></summary><blockquote>

If such a relation exists, then yes, it should be used. This is for cases where no such relations exists yet and would only be created for the sake of being able to connect some entity with a collection.
</blockquote></details>

Hm, wouldn't it be a good rule of thumb to mint an API-specific property for any such case? I think that is precisely what you did in events example...

---

*[drafts/use-cases/5.creating-new-event.md, line 29 at r1](https://reviewable.io:443/reviews/hydracg/specifications/132#-KrT4ZeUK43qWAnpOI76:-KrWwfKH-Fadrl8xtVZ4:b-3sunog) ([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>

Think of it as a specialized link relation that Hydra clients understand natively. This is similar to how browsers use the `icon` or `stylesheet` link relation. You could also have multiple `manages` blocks that describe the relationship between the referencing entity and the collection members in more detail. See the [page on the wiki](https://www.w3.org/community/hydra/wiki/Avoid_that_collections_break_relationships) where we worked on this (here's the [summary](https://www.w3.org/community/hydra/wiki/Collection_Design)).
</blockquote></details>

The problem with you analogy is that icon clearly defines the contents of the link's target. I'm not sure that is the case here.

---


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

Received on Monday, 14 August 2017 18:15:26 UTC