- From: Karol Szczepański via GitHub <sysbot+gh@w3.org>
- Date: Sun, 18 Mar 2018 22:18:29 +0000
- To: public-hydra-logs@w3.org
Review status: all files reviewed at latest revision, 8 unresolved discussions. --- *[drafts/use-cases/7.searching-events.md, line 72 at r3](https://reviewable.io:443/reviews/hydracg/specifications/154#-L7pnYSMDeJ6U5y0ECUB:-L7vAscO_PGrTAw-vyew:b62rfeo) ([raw file](https://github.com/hydracg/specifications/blob/fa23516a0e71bf50633726d839217103245d7544/drafts/use-cases/7.searching-events.md#L72)):* <details><summary><i>Previously, elf-pavlik (elf Pavlik) wrote…</i></summary><blockquote> to remove `hydra:search` we have to share such proposal with a mailing list, i could follow up with another PR just for that. As for `hydra:memberTemplate` - if we need it for some 'random access' type of feature we probably should add a Use Case for it first. </blockquote></details> In Heracles.ts there is already an integration test that uses `hydra:memberTemplate` to bind the collection with the direct member access [here](https://github.com/HydraCG/Heracles.ts/blob/master/integration-tests/HydraClient.spec.ts#L167). With this predicate I could _attach_ an operation that sits under the IRI template directly to the collection itself without any additional intermediate beings. --- *Comments from [Reviewable](https://reviewable.io:443/reviews/hydracg/specifications/154)* <!-- Sent from Reviewable.io --> -- GitHub Notification of comment by alien-mcl Please view or discuss this issue at https://github.com/HydraCG/Specifications/pull/154#issuecomment-374056987 using your GitHub account
Received on Sunday, 18 March 2018 22:18:38 UTC