- From: elf Pavlik via GitHub <sysbot+gh@w3.org>
- Date: Wed, 01 Nov 2017 20:45:20 +0000
- To: public-hydra-logs@w3.org
Review status: all files reviewed at latest revision, 12 unresolved discussions, some commit checks broke. --- *[drafts/use-cases/5.1.creating-event-with-put.md, line 72 at r1](https://reviewable.io:443/reviews/hydracg/specifications/143#-KxchCDgCDQQ4nzkMnf4:-KxtIJWPBtS6gcrIvhEz:bwrykej) ([raw file](https://github.com/hydracg/specifications/blob/f03e3028e6417adf2767a44c0c854b4af3b5fb4d/drafts/use-cases/5.1.creating-event-with-put.md#L72)):* <details><summary><i>Previously, lanthaler (Markus Lanthaler) wrote…</i></summary><blockquote> If you have a IRI template, the IRI isn't opaque anymore. You describe it's structure with the template... and thus it is also necessary to describe what the variables stand for. </blockquote></details> I agree with your point about opacity, I mostly meant that variable in the IRI doesn't have to match any value of 'property' in a payload. It looks like latest revision has `schema:name`which I think can work for 'slug'. I will still like to eventually like example with unique identifier after brainstorming it in #145 --- *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-341236735 using your GitHub account
Received on Wednesday, 1 November 2017 20:45:23 UTC