- From: Karol Szczepański via GitHub <sysbot+gh@w3.org>
- Date: Wed, 14 Mar 2018 07:35:29 +0000
- To: public-hydra-logs@w3.org
Well - in my opinion actions won't resolve that issue you've pointed. Action does not tell the client on how to build a resulting request - which details should go into the IRI template and which into the body. Indeed, client shouldn't need prior knowledge telling him to expand the operation with details or not, but I'm worried that there will be situations when this snipped: ```javascript client.invoke(operation, event); ``` will be enough - operation would have an IRI template that expects variables provided from outside of the `event` - what would client do in that scenario? I believe we've touched an issue we had a very brief chat on before - operation (or action, doesn't matter) is neither only it's body nor it's URL(template) - it's both (or even more for other protocols). Either operation or action should have a complete description on how to build a proper request, which is missing here. I aknowledge actions to give some semantic hints to the client - in that scenario operation would be a mere request description, but both still lack a complete knowledge of how the request needs to be created. --- Review status: all files reviewed at latest revision, 6 unresolved discussions. --- *Comments from [Reviewable](https://reviewable.io:443/reviews/hydracg/specifications/154#-:-L7YPAlanlDHFwLTpHK3:b3x2oja)* <!-- 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-372929930 using your GitHub account
Received on Wednesday, 14 March 2018 07:36:16 UTC