{"action":"created","issue":{"url":"https://api.github.com/repos/linkeddata/SoLiD/issues/4","labels_url":"https://api.github.com/repos/linkeddata/SoLiD/issues/4/labels{/name}","comments_url":"https://api.github.com/repos/linkeddata/SoLiD/issues/4/comments","events_url":"https://api.github.com/repos/linkeddata/SoLiD/issues/4/events","html_url":"https://github.com/linkeddata/SoLiD/issues/4","id":70103112,"number":4,"title":"SEARCH and/or GET+Query method","user":{"login":"bblfish","id":124506,"avatar_url":"https://avatars.githubusercontent.com/u/124506?v=3","gravatar_id":"","url":"https://api.github.com/users/bblfish","html_url":"https://github.com/bblfish","followers_url":"https://api.github.com/users/bblfish/followers","following_url":"https://api.github.com/users/bblfish/following{/other_user}","gists_url":"https://api.github.com/users/bblfish/gists{/gist_id}","starred_url":"https://api.github.com/users/bblfish/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bblfish/subscriptions","organizations_url":"https://api.github.com/users/bblfish/orgs","repos_url":"https://api.github.com/users/bblfish/repos","events_url":"https://api.github.com/users/bblfish/events{/privacy}","received_events_url":"https://api.github.com/users/bblfish/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":28,"created_at":"2015-04-22T11:37:21Z","updated_at":"2015-06-05T20:15:05Z","closed_at":"2015-06-05T19:55:23Z","body":"In the section \"Reading data using SPARQL\" I suggest instead using the SEARCH METHOD  ( see [the recent draft-snell-search-method-00 RFC](http://www.ietf.org/id/draft-snell-search-method-00.txt) which is being discussed [on the HTTP mailing list](https://lists.w3.org/Archives/Public/ietf-http-wg/2015AprJun/0157.html) currently and that is gaining momentum )\r\n \r\nI have implemented that already in rww-play as described in that [curl interaction page]( https://github.com/read-write-web/rww-play/wiki/Curl-Interactions)\r\n\r\n```sh\r\n $ curl -X SEARCH -k -i -H \"Content-Type: application/sparql-query; charset=UTF-8\" \\\r\n    --cert ../eg/test-localhost.pem:test \\\r\n    --data-binary @../eg/couch.sparql https://localhost:8443/2013/couch\r\nHTTP/1.1 200 OK\r\nContent-Type: application/sparql-results+xml\r\nContent-Length: 337\r\n\r\n<?xml version='1.0' encoding='UTF-8'?>\r\n<sparql xmlns='http://www.w3.org/2005/sparql-results#'>\r\n    <head>\r\n        <variable name='D'/>\r\n    </head>\r\n    <results>\r\n        <result>\r\n            <binding name='D'>\r\n                <literal datatype='http://www.w3.org/2001/XMLSchema#string'>Comfortable couch in Artist Stables</literal>\r\n            </binding>\r\n        </result>\r\n    </results>\r\n</sparql>\r\n```\r\n\r\nGiven that most other WebDAV methods are implemented ( see issue #3 ) this should be an easy addition, and seems less ad hoc than what is currently being suggested namely\r\n\r\n```HTTP\r\nGET /data/ HTTP/1.1\r\nHost: example.org\r\nQuery: SELECT * WHERE { ?s ?p ?o . }\r\n```"},"comment":{"url":"https://api.github.com/repos/linkeddata/SoLiD/issues/comments/109427691","html_url":"https://github.com/linkeddata/SoLiD/issues/4#issuecomment-109427691","issue_url":"https://api.github.com/repos/linkeddata/SoLiD/issues/4","id":109427691,"user":{"login":"RubenVerborgh","id":675313,"avatar_url":"https://avatars.githubusercontent.com/u/675313?v=3","gravatar_id":"","url":"https://api.github.com/users/RubenVerborgh","html_url":"https://github.com/RubenVerborgh","followers_url":"https://api.github.com/users/RubenVerborgh/followers","following_url":"https://api.github.com/users/RubenVerborgh/following{/other_user}","gists_url":"https://api.github.com/users/RubenVerborgh/gists{/gist_id}","starred_url":"https://api.github.com/users/RubenVerborgh/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/RubenVerborgh/subscriptions","organizations_url":"https://api.github.com/users/RubenVerborgh/orgs","repos_url":"https://api.github.com/users/RubenVerborgh/repos","events_url":"https://api.github.com/users/RubenVerborgh/events{/privacy}","received_events_url":"https://api.github.com/users/RubenVerborgh/received_events","type":"User","site_admin":false},"created_at":"2015-06-05T20:15:05Z","updated_at":"2015-06-05T20:15:05Z","body":"> I am writing client apps that sometimes need small portions of a graph to do the rendering quickly.\r\n\r\nI could see this working for smaller graphs, where it wouldn't matter if you accidentally got the whole graph. Then there's not much difference between the specific resource \"query on dataset\" and the generic resource \"dataset\". But not as a general principle for larger datasets. And then still there's the issue of caches needing to key on (URL, query-languge, query). So as such, I don't see much benefit to the whole approach.\r\n\r\nLet's close this discussion for now, I think we understand each other's viewpoints clearly and we agree to disagree :wink: Thanks for taking the time to write."}}