- From: Karol Szczepański via GitHub <sysbot+gh@w3.org>
- Date: Sun, 05 Nov 2017 18:53:47 +0000
- To: public-hydra-logs@w3.org
Would it be OK then to assume that `hydra:Link` is a shortcut of a `hydra:Operation` with `hydra:method` set to `GET`? As for the `hydra:accept` - we already have `hydra:expects`. Why not loosening it to something more generic than `hydra:Class`, let's say `hydra:Resource`. This way you could introduce various ways of describing what's expected, i.e. resource of type `hydra:Class` would imply an RDF resource, but `hydra-ext:HttpCompliantResource` would have a description for HTTP protocol specific stuff like content type, etc. -- GitHub Notification of comment by alien-mcl Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/149#issuecomment-341995800 using your GitHub account
Received on Sunday, 5 November 2017 18:53:51 UTC