- From: Karol Szczepański <karol.szczepanski@gmail.com>
- Date: Fri, 18 Sep 2015 20:53:01 +0200
- To: Ruben Verborgh <ruben.verborgh@ugent.be>
- Cc: "public-hydra@w3.org" <public-hydra@w3.org>
Received on Friday, 18 September 2015 18:53:33 UTC
Hi Ruben Bu Hydra does not allow me to document that my API expects/returns in a given operation something else than a hydra:Class. I'd like to have a possibility to express that in my very operation a non-RDF resource is also in place. I could put as a value of a hydra:expects an rdf:Resource or something else, but still reasoner will end up with a hydra:Class which will be untrue. BTW. I'm looking forward for a collections discussion. I've got almost ready a C# ReST self documenting API ready and few ideas to share. Regards Karol Szczepański <div>-------- Oryginalna wiadomość --------</div><div>Od: Ruben Verborgh <ruben.verborgh@ugent.be> </div><div>Data:18.09.2015 20:19 (GMT+01:00) </div><div>Do: Karol Szczepański <karol.szczepanski@gmail.com> </div><div>DW: public-hydra@w3.org </div><div>Temat: Re: 'expects' return value per status code? </div><div> </div>Hi Karol, > I'd like my API to accept i.e. Excel document or whatever file I'd like it to send/receive. Why would that not be possible? Hydra describes the contents of the resource, not what the representation should look like. I.e., you would say "send me a resource with details about a person", and this resource could be represented as JSON-LD, plain text, Excel… (of course the server wouldn't support just any format, but it's important to distinguish between resources and representations). Best, Ruben
Received on Friday, 18 September 2015 18:53:33 UTC