- From: Karol Szczepański via GitHub <sysbot+gh@w3.org>
- Date: Sun, 15 Apr 2018 18:09:20 +0000
- To: public-hydra-logs@w3.org
I strongly agree with @tpluscode. I'd prefer to move towards some more generic request templating mechanism, where server would define what goes where (i.e. this value goes into the body, this into the header and that into an URL). I recall we've touched this approach during the last call as it would bind all pieces altogether (operation extended with a body/header template as a description of the request, IRI template as description of the URL and action as semantic description of what is going to happen). Such approach will allow server to define whether it prefers i.e. HTTP LINK/UNLINK or some specific class expected within the body or some other variation. -- GitHub Notification of comment by alien-mcl Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/161#issuecomment-381425970 using your GitHub account
Received on Sunday, 15 April 2018 18:09:28 UTC