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

Review status: 0 of 1 files reviewed at latest revision, 15 unresolved discussions.

---

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

> all look-ups should be recursive within current resource. It should also use API documentation obtained at the very beginning.

that's a twist :smile: 
</blockquote></details>

If the `http://example.com/vocab/createEvent` property doesn't matter, can we replace it with `rdfs:seeAlso` not to cause false impression that it does matter?
If we decide that we need to use some meaningful property, then we can look at how client would rely on it and what it should mean and how do we name it.
I don't think we can require server to include the template and all operations this template supports inline, IMO representation can just include IRI to the template and client should have capability to "follow its nose" and retrieve that template and operations its support. In that case even recursive traversal of particular representation will not work.

---

*[drafts/use-cases/5.1.creating-new-event-indirectly.md, line 64 at r1](https://reviewable.io:443/reviews/hydracg/specifications/143#-KxYcL7VkgLlvZsRJlA4:-KxhOklnGTQ6C5Rkwy3D:bo6velu) ([raw file](https://github.com/hydracg/specifications/blob/f03e3028e6417adf2767a44c0c854b4af3b5fb4d/drafts/use-cases/5.1.creating-new-event-indirectly.md#L64)):*
<details><summary><i>Previously, alien-mcl (Karol Szczepański) wrote…</i></summary><blockquote>

I don't  have any specific likes or dislikes for what was written above - just don't let us forget we shouldn't neither forbid nor enforce anything specific. Examples by @tpluscode could happen
</blockquote></details>

If we change method in that snippet from `PUT` to `POST`, how does the client know if it can use that resource just one and needs to refetch the collection to get new IRI before each time it wants to add to it (`PUT`) or it can continue using that resource (`POST`)

---


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

Received on Monday, 30 October 2017 13:13:43 UTC