- From: Karol Szczepański via GitHub <sysbot+gh@w3.org>
- Date: Tue, 22 Jan 2019 20:03:08 +0000
- To: public-hydra-logs@w3.org
To revive this PR, let me attach a diagram of how do I see this matter. In general, I feel that additional predicate `action` is redundant (as stated earlier) and extending an `operation` with some features would be enough. The diagram below adds these elements: - returnsHeader - predicate for pointing returned header names - expectsHeader - predicate for pointing expected header names - target - explicit target of the operation (either Link or TemplatedLink - MediaTypedResource - dummy for describing expected/returned resource that is not an RDF class - mediaType - predicate for pointing an expected/returned resource's media type These elements are changed: - returns - range changed from Class to Resource - expects - range changed from Class to Resource ![hydra 1 1](https://user-images.githubusercontent.com/8111925/51562042-1862ed00-1e89-11e9-8050-f50d2de4e335.png) -- GitHub Notification of comment by alien-mcl Please view or discuss this issue at https://github.com/HydraCG/Specifications/pull/154#issuecomment-456542718 using your GitHub account
Received on Tuesday, 22 January 2019 20:03:10 UTC