- From: Karol Szczepański via GitHub <sysbot+gh@w3.org>
- Date: Thu, 05 Oct 2017 17:27:43 +0000
- To: public-hydra-logs@w3.org
Hmm. I grow up to think about semantic actions. Indeed it would make the client much simplier. I tried to start developing #141 and I've stumbled upon a choice: complicated logic on how to perform a simple operation of adding a resource to the collection or simple marked operation teling client exactly on what to do. Benefit would be to decouple logic of of the HTTP protocol, enabling applicability to other protocols (in theory at least). These would limit to very basic operations like deleting, updating, creating, linking and possibly searching/filtering. I believe these semantic operations should be defined in the spec either with native Hydra namespace based terms or explicit terms reused from other vocabularies. I wouldn't like to replace one difficult to implement logic related to protocol specific verbs with another complicated logic of figuring out which action does what (from the generic client point of view). I'll try to implement #141 with the semantic actions approach and we'll see how it behaves. -- GitHub Notification of comment by alien-mcl Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/134#issuecomment-334535135 using your GitHub account
Received on Thursday, 5 October 2017 17:27:35 UTC