- From: Barry Norton <barry.norton@ontotext.com>
- Date: Tue, 16 Apr 2013 20:31:21 +0100
- To: public-lod@w3.org
Agreed, this is a non-RESTful HTTP API to execute triple patterns. Furthermore, I'd say that the (rough) relational equivalent would be an API that lets you retrieve values from a nominated column where rows from a single table match a stated (singleton) primary key, or primary key values where the row matches a specified value in a specified column. Maybe useful in some cases, but pretty far from what people actually write (non-RESTful) APIs over a relational database to do. (Sorry, Luca, I know you're going for simplicity but you brought up the case of Web Services over RDBMSs). Barry > 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:31:49 UTC