- From: Tomasz Pluskiewicz via GitHub <sysbot+gh@w3.org>
- Date: Mon, 30 Oct 2017 14:42:27 +0000
- To: public-hydra-logs@w3.org
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:-KxdjRvGzIJPYXnHW7Z8:b-5r7r1e) ([raw file](https://github.com/hydracg/specifications/blob/f03e3028e6417adf2767a44c0c854b4af3b5fb4d/drafts/use-cases/5.1.creating-new-event-indirectly.md#L34)):* <details><summary><i>Previously, elf-pavlik (elf Pavlik) wrote…</i></summary><blockquote> 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. </blockquote></details> That's a new feature I think. But including those operations in ApiDocumentation should already be possible with SupportedProperties --- *Comments from [Reviewable](https://reviewable.io:443/reviews/hydracg/specifications/143)* <!-- Sent from Reviewable.io --> -- GitHub Notification of comment by tpluscode Please view or discuss this issue at https://github.com/HydraCG/Specifications/pull/143#issuecomment-340465184 using your GitHub account
Received on Monday, 30 October 2017 14:42:29 UTC