- From: elf Pavlik via GitHub <sysbot+gh@w3.org>
- Date: Sun, 29 Oct 2017 16:55:24 +0000
- To: public-hydra-logs@w3.org
Review status: all files reviewed at latest revision, 15 unresolved discussions. --- *[drafts/use-cases/5.1.creating-new-event-indirectly.md, line 42 at r1](https://reviewable.io:443/reviews/hydracg/specifications/143#-KxcW88cm2en7sVc9HI0:-Kxd0uoYYuoD9HbGdK9B:bt1asx5) ([raw file](https://github.com/hydracg/specifications/blob/f03e3028e6417adf2767a44c0c854b4af3b5fb4d/drafts/use-cases/5.1.creating-new-event-indirectly.md#L42)):* <details><summary><i>Previously, lanthaler (Markus Lanthaler) wrote…</i></summary><blockquote> If it would be a concrete resource, it wouldn't create an Event, but replace that resource. </blockquote></details> In one of the issues, we discussed that server could provide to client concrete IRI for new resource, so the resource doesn't exist yet and GET on that IRI provided by the server would result in 404 https://github.com/HydraCG/Specifications/issues/134#issuecomment-335028831 --- *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-340276734 using your GitHub account
Received on Sunday, 29 October 2017 16:55:26 UTC