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 64 at r1](https://reviewable.io:443/reviews/hydracg/specifications/143#-KxYcL7VkgLlvZsRJlA4:-KxeOrq_QLjDrAboTdg3:b3fowp7) ([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>

> I can't really think of situation where for collection we would have a resource and not a template for purpose of creating new members

Like I described in another comment -> server can mint id's for new resources so that creating new members is idempotent

``` json
{
  "@id": "/comment/aaa-bbb-ccc",
  "hydra:add": {
    "@id": "/comment/xxx-yyy-zzz",
    "hydra:operation": [{
      "method": "PUT"
    }]
  }
}
```

The `xxx-yyy-zzz` would be random GUID every time. Transient unless PUT. 
</blockquote></details>

This may work for something like 'Like' a movie etc. where movie would link to a not yet existing resource which once created would represent like by authenticated person (Vimeo and many other APIs style). For a collection to specify a way just add a one single resource to it doesn't seem practical at all. I can't imagine any service doing that since it would require client to re-request the collection every time before adding a new resource to it just to get a new IRI.

---


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

Received on Sunday, 29 October 2017 23:17:39 UTC