Re: 'expects' return value per status code?

Hi Victor

I've stumbled with issue of expecting or returning something completely non
RDF, i.e. I'd like my API to accept i.e. Excel document or whatever file
I'd like it to send/receive. Unfortunately current state of Hydra seems not
to support these scenarios. I'd stte that hydra:Class should be downgraded
to i.e. hydra:Resource or in general a resource (with few additional
properties that would allow to describe i.e. by media type or as you'd like
to have a status code).

I strongly believe that semantic description of the ReSTful APIs is the
bulzeye, but I also strongly believe that this description should not limit
only to describing semantic APIs.

Regards

Karol Szczepański

2015-09-17 15:36 GMT+02:00 Charpenay, Victor (ext) <
victor.charpenay@siemens.com>:

> Hi everybody,
>
> as I was designing a Hydra spec, I stumbled upon this little issue: I have
> different expected return values, depending on the status code that is
> responded.
>
> Has anybody already raised this issue? Would it make sense to change the
> range of ‘hydra:expects’ so that it could include both a
> StatusCodeDescription and a hydra:Class?
>
> Sincerely,
> Victor Charpenay
>
> Siemens AG
> Corporate Technology
> Research and Technology Center
> CT RTC NEC ITH-DE
> Otto-Hahn-Ring 6
> 81739 München, Deutschland
> *mailto:victor.charpenay@siemens.com* <victor.charpenay@siemens.com>
>
> Siemens Aktiengesellschaft: Vorsitzender des Aufsichtsrats: Gerhard
> Cromme; Vorstand: Joe Kaeser, Vorsitzender; Roland Busch, Lisa Davis, Klaus
> Helmrich, Janina Kugel, Siegfried Russwurm, Ralf P. Thomas; Sitz der
> Gesellschaft: Berlin und München, Deutschland; Registergericht: Berlin
> Charlottenburg, HRB 12300, München, HRB 6684; WEEE-Reg.-Nr. DE 23691322
>
>
>