Kingsley Idehen
Kingsley Idehen
> @imitko @pkleef @openlink @IvanMikhailov -- Please have a look at this. Where is the SPARQL Query Results URL for recreating the problem? None of the links in the stackoverflow...
> Our SPARQL endpoint is open to the public for now. Here's a URL to the query with duplicate results: > > https://kg.oceanproteinportal.org/sparql?default-graph-uri=&query=PREFIX+opp%3A+%3Chttp%3A%2F%2Fschema.oceanproteinportal.org%2Fv2%2F%3E%0D%0APREFIX+sosa%3A+%3Chttp%3A%2F%2Fwww.w3.org%2Fns%2Fsosa%2F%3E%0D%0ASELECT+DISTINCT+%3Flabel+%3Fdepth+%3Fstation%0D%0AWHERE+%7B+%0D%0A++%3Curn%3Aopp%3Adataset%3Ametzyme-0.2%3E+opp%3AstoresResultsForSample+%3Fsample+.%0D%0A++++%3Fsample+rdfs%3Alabel+%3Flabel+.+%0D%0A++++FILTER+REGEX%28%3Flabel%2C+%22CID%22%29+.%0D%0A++++%3Fsample+sosa%3AisSampleOf+%3Ffeature+.%0D%0A++++%3Ffeature+opp%3Adepth+%3Fdepth+.%0D%0A++++%3Ffeature+opp%3AinVicinityOfStation+%3FstationInfo+.%0D%0A++++%3FstationInfo+opp%3AstationName+%3Fstation+.%09%0D%0A%7D%0D%0AORDER+BY+%3Flabel&should-sponge=&format=text%2Fhtml&timeout=0&debug=on [Here's a rendition](https://kg.oceanproteinportal.org/sparql?default-graph-uri=&query=PREFIX+opp%3A+%3Chttp%3A%2F%2Fschema.oceanproteinportal.org%2Fv2%2F%3E%0D%0APREFIX+sosa%3A+%3Chttp%3A%2F%2Fwww.w3.org%2Fns%2Fsosa%2F%3E%0D%0ASELECT+DISTINCT+%3Fg+%3Flabel+%3Fdepth+%3Fstation%0D%0AWHERE+%7B+%0D%0A++graph+%3Fg+%7B%0D%0A++%3Curn%3Aopp%3Adataset%3Ametzyme-0.2%3E+opp%3AstoresResultsForSample+%3Fsample+.%0D%0A++++%3Fsample+rdfs%3Alabel+%3Flabel+.+%0D%0A++++FILTER+REGEX%28%3Flabel%2C+%22CID%22%29+.%0D%0A++++%3Fsample+sosa%3AisSampleOf+%3Ffeature+.%0D%0A++++%3Ffeature+opp%3Adepth+%3Fdepth+.%0D%0A++++%3Ffeature+opp%3AinVicinityOfStation+%3FstationInfo+.%0D%0A++++++++%3FstationInfo+opp%3AstationName+%3Fstation+.%09%7D%0D%0A%7D%0D%0AORDER+BY+DESC%28%3Flabel%29%0D%0A&should-sponge=&format=text%2Fhtml&timeout=360000&debug=on) that uses GRAPH ?g...
Extending the timeout parameter increases the time allotted to producing the query solution. This feature is critical to enabling the whole world use DBpedia rather than specific queries monopolizing processing...
This isn't a false result. This is a solution to the query within the constraints of a timeout. The server should indicate via HTTP response metadata the nature of the...
On 12/3/13 9:18 AM, Jörn Hees wrote: > Thanks, the time limit explains a bit, but this "feature" is highly > confusing if not dangerous because the user (in this...
On 12/4/13 6:50 AM, Jörn Hees wrote: > one addenum, sorry: > it should be optional to get partial results, not an implicit default > that you then have to...
On 12/4/13 6:49 AM, Jörn Hees wrote: > @kidehen https://github.com/kidehen neither of the links you provide > describe/warn of the reported problem: that counts can be wrong if a >...
On 12/9/13 12:37 PM, Jörn Hees wrote: > On 4 Dec 2013, at 14:09, Kingsley Idehen [email protected] > wrote: > > > It isn't right > > to assume DBpedia...
On 12/9/13 2:56 PM, Jörn Hees wrote: > On 9 Dec 2013, at 20:18, Kingsley Idehen [email protected] wrote: > > > You are reporting the fact that you are executing...
On 12/11/14 3:25 AM, Jindřich Mynarz wrote: > @kidehen : The only headers I see in > responses from Virtuoso are `Accept-Ranges`, `Cache-Control`, > `Expires`, `Server`, `Connection`, `Content-Length`, `Content-Type` >...