Re: Restpark - Minimal RESTful API for querying RDF triples

(Yes, Linked Data API is cool!, and thanks for getting back to the main subject, although I somehow doubt anyone is expecting to read anything about it in this thread now :-) )

Thanks Barry.
Thanks, Luca for adding the examples to the page.
Is there any reason why you don't provide a predicate (such as foaf:name) in the first query?
Don't you need to URLencode the URIs?
I think the final URI should have a ? instead of a & ?

I see you have limit in there - was that in the original?
If not, then this is a slippery slope.
You wanted something simple, but in general, I have a feeling that you will keep adding things to your interface that will mean that you end up with something that looks remarkably like the Linked Data API, but will have just grown, rather than being designed from the start, which is usually better.

Cheers

On 16 Apr 2013, at 22:49, Barry Norton <barry.norton@ontotext.com>
 wrote:

> Apologies if Hugh's had an answer (I'm sitting on a train with patchy WiFi), but if not let me explain my speculation that the s/p/o parameters are all optional and, if missing, are 'match all' (hence my assertion about triple patterns). Am I on the right page there?
> 
> ----- Reply message -----
> From: "Hugh Glaser" <hg@ecs.soton.ac.uk>
> To: "Luca Matteis" <lmatteis@gmail.com>
> Cc: "Hugh Glaser" <hg@ecs.soton.ac.uk>, "<public-lod@w3.org>" <public-lod@w3.org>
> Subject: Restpark - Minimal RESTful API for querying RDF triples
> Date: Tue, Apr 16, 2013 4:32 PM
> 
> 
> Sure.
> But it isn't about the format - it's the content.
> I actually thought this was an April Fool to start with.
> I just can't work out what it returns, other than "found" or "not found", or similar.
> 
> On 16 Apr 2013, at 21:26, Luca Matteis <lmatteis@gmail.com>
> wrote:
> 
> > Hugh, I am actually still thinking about this. Was probably going to opt for JSON-LD.
> > 
> > 
> > On Tue, Apr 16, 2013 at 10:04 PM, Hugh Glaser <hg@ecs.soton.ac.uk> wrote:
> > I may be the only one, but I can't work out with any confidence what JSON your query returns.
> > My first assumption was that it would usually return only "found" or "not found".
> > 
> > Can you give me a real example of a Restpark URI with 3 URIs and the JSON returned?
> > You could add this to the web site.
> > 
> > Cheers
> > 
> > On 16 Apr 2013, at 18:52, Luca Matteis <lmatteis@gmail.com>
> >  wrote:
> > 
> > > I have recently created Restpark: http://lmatteis.github.io/restpark/
> > >
> > > It's my way of pushing a standard RESTful interface for accessing RDF data. Still in its very infancy but hopefully it can be something to consider. I personally think the Semantic Web community desperately needs a simpler protocol for querying RDF, along side SPARQL. I have nothing against SPARQL, it's an important standard to have. But something simpler and RESTful needs to be part of the Semantic Web stack.
> > >
> > > The entire web community is used to consuming APIs as simple HTTP requests (REST). Would you imagine GitHub, Flickr, or any other web-service API actually exposing SQL instead of their RESTful API? It would make things a bit more complicated for third-parties in my opinion, but more importantly it would make things so much more complicated for services to implement.
> > >
> > > I would love to think what the community thinks about this.
> > >
> > > Best,
> > > Luca
> > 
> > 
> 
>

Received on Thursday, 18 April 2013 09:57:58 UTC