- From: Karol Szczepański via GitHub <sysbot+gh@w3.org>
- Date: Tue, 13 Mar 2018 20:04:49 +0000
- To: public-hydra-logs@w3.org
Review status: all files reviewed at latest revision, 6 unresolved discussions. --- *[drafts/use-cases/1.1.security-considerations.md, line 35 at r3](https://beta.reviewable.io/reviews/hydracg/specifications/154#-L5Fjs7pVaFH-CFN_F4A:-L7Vwgyo9PAxdbPnT2Dp:b-r99ruq) ([raw file](https://github.com/hydracg/specifications/blob/fa23516a0e71bf50633726d839217103245d7544/drafts/use-cases/1.1.security-considerations.md#L35)):* <details><summary><i>Previously, lanthaler (Markus Lanthaler) wrote…</i></summary><blockquote> Adding it to the action wouldn't work as there might be multiple operations allowing you to perform the action. The use case at hand would be using different protocols like either sending an HTTP request or a GRPC request. </blockquote></details> Hmm. This just makes the benefits from action event less tempting. If it just to add some semantic to an operation, I think I preferred typing an operation - this way you could have single operation marked with multiple semantics (i.e. same operation adds and creates collection items). BTW. How would you pick the operation matching a desired protocol? --- *Comments from [Reviewable](https://beta.reviewable.io/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-372800152 using your GitHub account
Received on Tuesday, 13 March 2018 20:04:53 UTC