Re: [Specifications] Add Use Case: Creating events indirectly (ie. with PUT)

Review status: 0 of 1 files reviewed at latest revision, 6 unresolved discussions, some commit checks failed.

---

*[drafts/use-cases/5.1.creating-new-event-indirectly.md, line 58 at r1](https://reviewable.io:443/reviews/hydracg/specifications/143#-KxY28Opn5nMlgaMrFGV-r1-58:-KxZrzjoJB8httH2Pqxs:b-grulfr) ([raw file](https://github.com/hydracg/specifications/blob/f03e3028e6417adf2767a44c0c854b4af3b5fb4d/drafts/use-cases/5.1.creating-new-event-indirectly.md#L58)):*
<details><summary><i>Previously, tpluscode (Tomasz Pluskiewicz) wrote…</i></summary><blockquote>

Interesting points, but I think they are outside of the scope of this PR. Best let's continue this discussion in a new issue or where we discuss the manages block. I merely copied the collection from Use Case 5.
</blockquote></details>

I agree that this PR does NOT introduce `manages` block here, I added it via https://github.com/HydraCG/Specifications/pull/132 and if we want to change it we should start dedicated Issue or PR for it

---

*[drafts/use-cases/5.1.creating-new-event-indirectly.md, line 64 at r1](https://reviewable.io:443/reviews/hydracg/specifications/143#-KxYcL7VkgLlvZsRJlA4:-KxZt5uGyFAoqSS6nmWU:b2otig2) ([raw file](https://github.com/hydracg/specifications/blob/f03e3028e6417adf2767a44c0c854b4af3b5fb4d/drafts/use-cases/5.1.creating-new-event-indirectly.md#L64)):*
<details><summary><i>Previously, tpluscode (Tomasz Pluskiewicz) wrote…</i></summary><blockquote>

Sure, I can agree with either. I used an API-specific property here because where I previously minted something in the `hydra` namespace and I thought it caused confusion :).

On the other hand, similar method can be employed to create resource outside the context of collections. I can think of an optional linked resource which can be created once but is not part of any collection. Would you also propose a generic `hydra` term for such uses?
</blockquote></details>

If you have some other specific Use Case, maybe you could describe it in depth, either in this PR, one of the open Issues or new PR. As I understand this Use Case we want to *create* a new resource of type *schema:Event* and have it appear as a member in this collection.

---


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


-- 
GitHub Notification of comment by elf-pavlik
Please view or discuss this issue at https://github.com/HydraCG/Specifications/pull/143#issuecomment-340221234 using your GitHub account

Received on Saturday, 28 October 2017 21:32:36 UTC