- From: Karol Szczepański via GitHub <sysbot+gh@w3.org>
- Date: Thu, 14 Feb 2019 21:08:07 +0000
- To: public-hydra-logs@w3.org
> The problem as I understand it, is that we'd want to describe > constraints for non-RDF payloads using RDF structures. We'd want to describe both that way. Currently by saying `hydra:returns some:Class` we're saying that the operation returns a resource that matches a specification (a specific class in that case). This _shortcut_ seems not well understood - the specification approach could make that statement more direct. It would also enable the vocabulary for non-RDF specifications and RDF specifications that could went far beyond simple class matching (in API documentations you could specify returned collection) -- GitHub Notification of comment by alien-mcl Please view or discuss this issue at https://github.com/HydraCG/Specifications/pull/186#issuecomment-463797038 using your GitHub account
Received on Thursday, 14 February 2019 21:08:09 UTC