Re: [Specifications] hydra:search with HTTP POST (#149)

I gave it many thoughts and I think this issue should be taken to another level - how to mint operations with IRI template.

I think current Heracles.ts implementation already allows this kind of constructs. I've started from an assumption that a link is actually a shortcut of an operation that is using GET by default.

```turtle
</api> hydra:collection </api/users>.
</api> api:users [
  hydra:IriTemplate;
  hydra:template "/api/users{?search}".

api:users a 
  rdfs:subPropertyOf hydra:search;
  hydra:operation [hydra:method "POST"].
```

This way we don't need to create any new terms and everything seems OK compared against existing vocabulary and it's constratins. The client could use either a direct collection, GET search results (as the `api:users` is sub-property of `search`) or POST same things as an optional alternative to GET based search.

What do you think about it? We could add a paragraph to the spec to clarify how to interprete such constructs.

-- 
GitHub Notification of comment by alien-mcl
Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/149#issuecomment-817321654 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Sunday, 11 April 2021 15:00:23 UTC