- From: elf Pavlik via GitHub <sysbot+gh@w3.org>
- Date: Mon, 14 Aug 2017 21:58:27 +0000
- To: public-hydra-logs@w3.org
Review status: all files reviewed at latest revision, 3 unresolved discussions. --- *[drafts/use-cases/0.intro.md, line 89 at r2](https://reviewable.io:443/reviews/hydracg/specifications/132#-KrWt32Z1UxZkNXLNAXm:-KrXdrB95u6yx22c-D0f:byvigx2) ([raw file](https://github.com/hydracg/specifications/blob/8c2db652e54f3e4ed52b855e05c73330d9d2d2ea/drafts/use-cases/0.intro.md#L89)):* <details><summary><i>Previously, lanthaler (Markus Lanthaler) wrote…</i></summary><blockquote> I don't remember whether we introduced the rule afterwards but I think we agreed to not have terms that differ only in their capitalization. Maybe we should revisit this at some point. </blockquote></details> captured in https://github.com/HydraCG/Specifications/issues/133 --- *[drafts/use-cases/1.1.security-considerations.md, line 18 at r2](https://reviewable.io:443/reviews/hydracg/specifications/132#-KrUSFWcxbytETQ1yIEc:-KrXjKLiBHWVcSKkLQQ5:b7f3y0o) ([raw file](https://github.com/hydracg/specifications/blob/8c2db652e54f3e4ed52b855e05c73330d9d2d2ea/drafts/use-cases/1.1.security-considerations.md#L18)):* <details><summary><i>Previously, lanthaler (Markus Lanthaler) wrote…</i></summary><blockquote> Yeah, it's exactly what I did in the events example.. but only because there was nothing else available. The goal is to create clients that "understand" these APIs to some degree so that they can figure out how to use them. If everyone mints property like `myvocab:events` only clients that have been written specifically for that API will understand them. If we have a generic mechanisms as the one Pavlik proposes here on the other hand, we can implement client libraries that can *find the collection that contains all events*. A custom link relation is only useful if it has some well-defined semantics that you can't convey otherwise. </blockquote></details> Since this PR proposes just one of possible solutions for the problem, I would like to suggest once again discussing and further clarifying the problem we try to address itself in https://github.com/HydraCG/Specifications/issues/126#issuecomment-322320409 --- *Comments from [Reviewable](https://reviewable.io:443/reviews/hydracg/specifications/132)* <!-- Sent from Reviewable.io --> -- GitHub Notification of comment by elf-pavlik Please view or discuss this issue at https://github.com/HydraCG/Specifications/pull/132#issuecomment-322321389 using your GitHub account
Received on Monday, 14 August 2017 21:58:28 UTC