- From: Tomasz Pluskiewicz via GitHub <sysbot+gh@w3.org>
- Date: Sun, 05 Nov 2017 16:27:21 +0000
- To: public-hydra-logs@w3.org
I think you managed to smoosh many separate issues in here :) First let's start with the `search` link. Does is link to the `/issues` collection (to itself)? I think what you're looking for is simply ``` json { "@id": "http://api.example.com/issues", "operation": [ { "@type": [ "Operation", "schema:SearchAction" ], "method": "POST", "???:contentType": "application/sparql-query" } ] } ``` The `???:contentType` relation is a different story. I'm pretty sure this has been brought up on already on the list and there's #22. It mentions `schema:contentType` but it has some extra semantics. I'd rather have our own under `hydra` namespace. Maybe `hydra:accept` would make sense akin to HTTP? It could also allow an array. -- GitHub Notification of comment by tpluscode Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/149#issuecomment-341985623 using your GitHub account
Received on Sunday, 5 November 2017 16:28:00 UTC