Re: List of supported use cases for compliant and conditionally compliant client

• From: Ruben Verborgh <ruben.verborgh@ugent.be>
• Date: Fri, 17 Jun 2016 09:11:45 -0700
• To: Dietrich Schulten <ds@escalon.de>
• Cc: Hydra <public-hydra@w3.org>
• Message-Id: <544F850B-01F9-4C94-8A01-51A0E105F246@ugent.be>

Hi Dietrich,

Interesting to have such a list!

> 4. As a programmer, I want to use the client to POST to the API by
> giving it linked data to POST and a path of predicates which leads to a
> representation that has a POST hydra operation.
> 
> 5. As a programmer, I want to use the client to PUT data to the API by
> giving it linked data to PUT (replace) and a path of predicates which
> leads to a representation that has a PUT hydra operation.
> 
> 6. As a programmer, I want to use the client to PATCH (partial update) a
> resource by giving it a path of predicates which leads to a
> representation that has a PATCH hydra operation. (e.g. setting an
> :eventStatus to :EventCancelled)

IMHO, the above 3 cases are to specific.
As a programmer, you don't want to POST;
you want to create a new resource or change an existing one.

This might or might not happen with POST in the back,
but this should not be of your concern at the Hydra level.

Ruben

Received on Friday, 17 June 2016 16:12:19 UTC