- From: Karol Szczepański via GitHub <sysbot+gh@w3.org>
- Date: Wed, 13 Feb 2019 20:30:16 +0000
- To: public-hydra-logs@w3.org
> I think we're opening a can of worms with changes to the returns property. But with current hydra specification it also means that server may return something completely different than declared `returns` specification. Client should always check what it did receive. > Class is itself subClass of Resource. Hence, nothing really changes in principle. It does. See that example: ```n3 some:operation hydra:returns some:mediaTypedResource . ``` With range of `hydra:Class`, you've automatically raised `some:mediaTypedResource` to a `hydra:Class`, which is untrue. I wound like to leave `some:mediaTypedResource` as pure `hydra:Resource`. -- GitHub Notification of comment by alien-mcl Please view or discuss this issue at https://github.com/HydraCG/Specifications/pull/186#issuecomment-463356224 using your GitHub account
Received on Wednesday, 13 February 2019 20:30:18 UTC