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

Yes, I agree that operations supported by property should be enough. Rather than having a concrete URI as the object of a predicate, we have a template. The client must construct the final URI first and then perform any of the supported operation 🎉 

The detail is, like you say, the actual action of minting the identifier. Search is easier, but in the past I may have proposed this method also for creating new resources

```turtle
# ApiDocumentation
api:users hydra:supportedOperation 
[
  hydra:title "Create User" ;
  hydra:method "PUT" ;
] .

# Entrypoint
<> api:users [
  hydra:template "/user/{name}" ;
  hydra:mapping
  [
    hydra:variable "name" ;
    hydra:property schema:name ;
  ] ;
] .

# New user to be created
[] schema:name "John" .
```

Given the resources above, the client would make a request to `/user/John`, because the value of `schema:name` property ia mapped to the variable `name` in the URI template. This is in fact the same method I prefer to collection filtering using templates too.

---

Besides, I think it only needs one change (unless you mean inline operation)

```diff
-hydra:operation [hydra:method "POST"]
-hydra:supportedOperation [hydra:method "POST"]
```

-- 
GitHub Notification of comment by tpluscode
Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/149#issuecomment-817323651 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:13:04 UTC