- From: Karol Szczepański via GitHub <sysbot+gh@w3.org>
- Date: Tue, 13 Feb 2018 20:02:04 +0000
- To: public-hydra-logs@w3.org
Review status: 0 of 8 files reviewed at latest revision, 3 unresolved discussions. --- *[drafts/use-cases/1.1.security-considerations.md, line 35 at r3](https://reviewable.io:443/reviews/hydracg/specifications/154#-L5Fjs7pVaFH-CFN_F4A:-L5Fjs7pVaFH-CFN_F4B:b1eo15x) ([raw file](https://github.com/hydracg/specifications/blob/fa23516a0e71bf50633726d839217103245d7544/drafts/use-cases/1.1.security-considerations.md#L35)):* > ```Markdown > "method": "POST", > "expects": "schema:Event", > "target": "/api/events" > ``` I though it is the `action` that would have a target defined - `operation` would still be dependent on it's owner in that manner. This way we would leave operations compatible with current spec. Otherwise I don't see any benefit in introducing actions at all - we could incorporate all those details in operations as we do no i.e. in Heracles.ts (with adding `target` as this is the only part that's missing) --- *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-365386489 using your GitHub account
Received on Tuesday, 13 February 2018 20:02:40 UTC