W3C home > Mailing lists > Public > public-lod@w3.org > February 2010

Re: AW: Linked Data API

From: Dave Reynolds <dave.e.reynolds@googlemail.com>
Date: Thu, 25 Feb 2010 17:56:53 +0000
Message-ID: <4B86B9E5.9020004@gmail.com>
To: Chris Bizer <chris@bizer.de>
CC: 'Leigh Dodds' <leigh.dodds@talis.com>, 'Linking Open Data' <public-lod@w3.org>, 'Jeni Tennison' <jeni@jenitennison.com>
Hi Chris,

Yes, I think there is some relationship to Pubby, but some differences too.

As I understand it Pubby is mostly about serving up the individual 
resources REST style. The API-in-search-of-a-cool-name does support that 
but a key part of it is about serving up paged, filtered lists of of 

This simplified query mechanism, along with the JSON and XML formats, 
gives us easy programmatic access to the data sets for non-SPARQL, 
non-RDF developers.

What would you think about extending Pubby to support the proposed JSON 
and simple XML formats? Could be cool.


On 25/02/2010 17:08, Chris Bizer wrote:
> Hi Leigh,
> sounds like an interesting alternative to Pubby
> (http://www4.wiwiss.fu-berlin.de/pubby/) if I understand it right.
> Cheers,
> Chris
>> -----Ursprüngliche Nachricht-----
>> Von: public-lod-request@w3.org [mailto:public-lod-request@w3.org] Im
> Auftrag
>> von Leigh Dodds
>> Gesendet: Donnerstag, 25. Februar 2010 12:47
>> An: Linking Open Data
>> Cc: Jeni Tennison; Dave Reynolds
>> Betreff: Linked Data API
>> Hi all,
>> Yesterday, at the 2nd Linked Data London Meetup, Dave Reynolds, Jeni
>> Tennison and myself ran a workshop introducing some work we've been
>> doing around a "Linked Data API".
>> The API is intended to be a middle-ware layer that can be deployed
>> in-front of a SPARQL endpoint, providing the ability to create a
>> RESTful data access layer for accessing the RDF data contained in the
>> triple store. The middle-ware is configurable, and is intended to
>> support a range of different access patterns and output formats. "Out
>> of the box" the system provides delivery of the standard range of RDF
>> serialisations, as well as simple JSON and XML serializations for
>> descriptions of lists of resources. The API essentially maps
>> parameterized URLs to underlying SPARQL queries, mediating the content
>> negotiation of the results into a suitable format for the client.
>> The current draft specification is at:
>> http://purl.org/linked-data/api/spec
>> And there is now a mailing list available at:
>> http://code.google.com/p/linked-data-api/
>> We'd be interested in your feedback. Please join the list if you're
>> interested in discussing the API specification or collaborating on the
>> work and implementations.
>> Cheers,
>> L.
>> --
>> Leigh Dodds
>> Programme Manager, Talis Platform
>> Talis
>> leigh.dodds@talis.com
>> http://www.talis.com
Received on Thursday, 25 February 2010 17:57:34 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:16:03 UTC