Why is that a problem for query submissions using POST, in general? What s the problem with posted queries that get a response like this: 201 Created ...Message 1 of 40 , Feb 1, 2011View SourceWhy is that a problem for query submissions using POST, in general?What's the problem with posted queries that get a response like this:201 Created...Content-Location /query/x1lka2xjl2a8ksx....<query result>Any subsequent repeat queries could be served a 303Afaik, the main reason SPARQL queries are POST and not GET is because of the practical limitations on the length of a URL.Cheers,MikeOn Tue, Feb 1, 2011 at 12:12 AM, Eric J. Bowman <eric@...> wrote:
Bob Ferris wrote:REST has no concept of parent/child resources, particularly inferred
> What about a SPARQL endpoint that supports HTTP POST for every method
> handling? So the SPARQL endpoint resource would be treated as the
> "parent" resource of all resource that are stored in the triple
from URIs. Such relationships are established explicitly, through
linking. The problem with using POST for query submission, is that it
violates the Identification of Resources constraint -- query results
are resources of interest, so they need URIs.
Yahoo! Groups Links
<*> To visit your group on the web, go to:
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
... Oops again, sorry, it was never like this with the telegraph... Let s take this to a new ... Although I d like to hear your opinion on how SPARQLMessage 40 of 40 , Feb 2, 2011View SourceOn 2 February 2011 15:40, Eric J. Bowman <eric@...> wrote:
> Danny Ayers wrote:Oops again, sorry, it was never like this with the telegraph...
>> [oops, I meant to send this to the list, that yahoo interface is
> Note that you're also quoting me, not Bob...
Let's take this to a new
> thread, shall we?Although I'd like to hear your opinion on how SPARQL endpoints aren't
RESTful, I haven't really got anything to add on that aspect.