Forgot reply all
Original Message
Subject: Re: Public SPARQL endpoints:managing (mis)-use and
communicating limits to users.
Date: Thu, 18 Apr 2013 23:21:46 +0200
From: Jerven Bolleman
To: Rob Warren
Hi Rob,
There is a fundamental problem with HTTP status codes.
Lets say
On 18-Apr-13, at 8:53 AM, Jerven Bolleman wrote:
Many of the current public SPARQL endpoints limit all their users to
queries of limited CPU time.
But this is not enough to really manage (mis) use of an endpoint.
Also the SPARQL api being http based
suffers from the problem that we first sen
Hi,
On Fri, Apr 19, 2013 at 8:49 AM, Jerven Bolleman
wrote:
> Original Message
> Subject: Re: Public SPARQL endpoints:managing (mis)-use and communicating
> limits to users.
> Date: Thu, 18 Apr 2013 23:21:46 +0200
> From: Jerven Bolleman
> To: Rob Warren
>
> Hi Rob,
>
> There
*** apologies for cross-posting ***
Dear all,
We are proud to announce the launch of the W3C Research Object for
Scholarly Communication (ROSC) Community Group [1] (#rosc).
The primary goal of the Community Group is to provide a platform for
scholars, librarians, publishers, archivists and p
And sorry, forgot the two links. Here you are;
[1] http://www.w3.org/community/rosc/
[2] http://www.w3.org/community/rosc/rosc-community-group-charter/
Cheers,
Jun
On 19/04/13 10:16, Jun Zhao wrote:
*** apologies for cross-posting ***
Dear all,
We are proud to announce the launch of the W3
On 4/18/13 4:53 PM, Rob Warren wrote:
On 18-Apr-13, at 8:53 AM, Jerven Bolleman wrote:
Many of the current public SPARQL endpoints limit all their users to
queries of limited CPU time.
But this is not enough to really manage (mis) use of an endpoint.
Also the SPARQL api being http based
suffe
On 4/19/13 3:49 AM, Jerven Bolleman wrote:
Forgot reply all
Original Message
Subject: Re: Public SPARQL endpoints:managing (mis)-use and
communicating limits to users.
Date: Thu, 18 Apr 2013 23:21:46 +0200
From: Jerven Bolleman
To: Rob Warren
Hi Rob,
There is a fundament
On 4/19/13 4:20 AM, Leigh Dodds wrote:
Hi,
On Fri, Apr 19, 2013 at 8:49 AM, Jerven Bolleman
wrote:
Original Message
Subject: Re: Public SPARQL endpoints:managing (mis)-use and communicating
limits to users.
Date: Thu, 18 Apr 2013 23:21:46 +0200
From: Jerven Bolleman
To: Rob
Hi,
On Fri, Apr 19, 2013 at 11:55 AM, Kingsley Idehen
wrote:
> ...
> If you have OFFSET and LIMIT in use, you can reflect the new state of
> affairs when the next GET is performed i.e, lets say you have OFFSET 20 and
> LIMIT 20, the URL with OFFSET 40 is the request for the next batch of
> result
On 4/19/13 7:04 AM, Leigh Dodds wrote:
Hi,
On Fri, Apr 19, 2013 at 11:55 AM, Kingsley Idehen
wrote:
...
If you have OFFSET and LIMIT in use, you can reflect the new state of
affairs when the next GET is performed i.e, lets say you have OFFSET 20 and
LIMIT 20, the URL with OFFSET 40 is the requ
Kingsley,
On Thu, Apr 18, 2013 at 11:21 AM, Kingsley Idehen
wrote:
> The global Web is a functional Data Space equipped with a declarative query
> language based on the Web's architectural essence (URIs and HTTP). It can
> work, and will work. The challenge is getting folks to hone in to what
> p
25th OpenMath Workshop
Bath, UK
10 July 2013
co-located with CICM 2013
Submission deadline 7 June
http://www.cicm-conference.org/2013/cicm.php?event=openmath
OBJECTIVES
OpenMath (http://www.openmath.org) is a language for exchanging
mathematical formulae across applications (such as computer alg
On Apr 19, 2013, at 07:44, Mark Baker wrote:
> Kingsley,
>
> On Thu, Apr 18, 2013 at 11:21 AM, Kingsley Idehen
> wrote:
>> The global Web is a functional Data Space equipped with a declarative query
>> language based on the Web's architectural essence (URIs and HTTP). It can
>> work, and will
Hi Rob,
There is a fundamental problem with HTTP status codes.
Lets say a user submits a complex but small sparql request.
My server sees the syntax is good and starts to reply in good faith.
This means the server starts the http response and sends an 200 OK
Some results are being send
Howev
On Thu, Apr 18, 2013 at 9:23 AM, Andrea Splendiani
wrote:
> Hi,
>
> I think that some caching with a minimum of query rewriting would get read of
> 90% of the select{?s ?p ?o} where {?s?p ?o} queries.
>
> From a user perspective, I would rather have a clear result code upfront
> telling me: your
On 4/19/13 7:44 AM, Mark Baker wrote:
Kingsley,
On Thu, Apr 18, 2013 at 11:21 AM, Kingsley Idehen
wrote:
The global Web is a functional Data Space equipped with a declarative query
language based on the Web's architectural essence (URIs and HTTP). It can
work, and will work. The challenge is g
On 4/19/13 9:25 AM, Rob Warren wrote:
Hi Rob,
There is a fundamental problem with HTTP status codes.
Lets say a user submits a complex but small sparql request.
My server sees the syntax is good and starts to reply in good faith.
This means the server starts the http response and sends an 200 O
On 19-Apr-13, at 8:04 AM, Leigh Dodds wrote:
Hi,
On Fri, Apr 19, 2013 at 11:55 AM, Kingsley Idehen
wrote:
...
If you have OFFSET and LIMIT in use, you can reflect the new state of
affairs when the next GET is performed i.e, lets say you have
OFFSET 20 and
LIMIT 20, the URL with OFFSET 40 is
FINAL CALL FOR MAIN CONFERENCE PAPERS
-
The 12th International Semantic Web Conference
and the 1st Australasian Semantic Web Conference
21-25 October 2013, Sydney, Australia
http://www.iswc2013.semanticweb.org/
Deadlines approaching: May 1 for research track and
On Fri, Apr 19, 2013 at 9:25 AM, Rob Warren wrote:
>> Hi Rob,
>>
>> There is a fundamental problem with HTTP status codes.
>> Lets say a user submits a complex but small sparql request.
>>
>> My server sees the syntax is good and starts to reply in good faith.
>> This means the server starts the h
20 matches
Mail list logo
