- From: Luca Matteis <lmatteis@gmail.com>
- Date: Tue, 16 Apr 2013 21:29:00 +0200
- To: Mark Baker <distobj@acm.org>
- Cc: Linked Data community <public-lod@w3.org>
- Message-ID: <CALp38ENcdXyWvSbMwnRV90bQoksfhjSDwKfVE9rvUTKzW8R-cQ@mail.gmail.com>
Mark, true this isn't actually REST. I just felt that REST is such a buzzword these days for defining simple and easily implementable web services. Which is exactly what Restpark aims to be. Kingsley, it seems like you haven't used databases such as CouchDB that *only* expose an HTTP API (this on is actually fully RESTful). CouchDB is an entirely scalable and widely used database solution, so I don't fully understand your scaling argument. I totally understand that SPARQL is meant to "do it all" and that's obviously needed. The purpose of Restpark is not to "do it all" but simply to offer the basic features sufficient for many uses cases. On Tue, Apr 16, 2013 at 9:06 PM, Mark Baker <distobj@acm.org> wrote: > On Tue, Apr 16, 2013 at 1:52 PM, 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. > > Unfortunately, this isn't REST. REST APIs must use hypermedia; > > http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven > > A hypermedia solution would declare a form that described how to > construct a new URI which could be used to retrieve the data via GET. > The form would provide the parameter names (e.g. "subject") along with > their types (e.g. rdf:subject). > > Mark. >
Received on Tuesday, 16 April 2013 19:29:28 UTC