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

Review status: all files reviewed at latest revision, 1 unresolved discussion.

---

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

I think the client should provide interface to control JSON-LD context. We just need to make it clear that developer shouldn't make any assumptions about JSON-LD context in received payloads and aways make sure to provide desired context to the client.
I would propose that once we agree on using `manages` block in the use case we should address client interface details in a future PR to https://github.com/HydraCG/Heracles.ts which implementation follows work on use cases...
</blockquote></details>

Yeah, I share that concerns as we "leak" quite a lot of RDF concepts here. Perhaps renaming `manages` to `constraints` or something similar and trying to come up with something replacing `subject` and `object` would solve that (we could eventually look at [SHACL](https://www.w3.org/TR/shacl/) which recently became a W3C recommendation).

In the spirit of moving fast(er) I'd, howerver, like to propose to go ahead and merge this PR. If someone has a concrete proposal to improve this, it can be discussed in a separate PR. If no one objects, I'll merge this tomorrow.

---


*Comments from [Reviewable](https://reviewable.io:443/reviews/hydracg/specifications/132)*
<!-- Sent from Reviewable.io -->


-- 
GitHub Notification of comment by lanthaler
Please view or discuss this issue at https://github.com/HydraCG/Specifications/pull/132#issuecomment-322983103 using your GitHub account

Received on Thursday, 17 August 2017 06:43:09 UTC