On 4/16/13 3:31 PM, Barry Norton wrote:

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).

+1

Kingsley

Barry


On Tue, Apr 16, 2013 at 1:52 PM, Luca Matteis <[email protected]> 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.







--

Regards,

Kingsley Idehen 
Founder & CEO
OpenLink Software
Company Web: http://www.openlinksw.com
Personal Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca handle: @kidehen
Google+ Profile: https://plus.google.com/112399767740508618350/about
LinkedIn Profile: http://www.linkedin.com/in/kidehen





Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to