Re: AW: Linked Data API

Dave Reynolds wrote:
> 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 resources.
>
> 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.
>
> Dave
>

See  OData [1] it much closer and from a company that knows a lot about 
Data Access APIs (but has historically  struggled with platform 
independence).  On our front we are going to implement OData as a bridge 
mechanism between RDF and  MSFT approaches to Entity-Attribute-Value 
model data access.

Links:

1. http://www.odata.org/docs/[MC-APDSU].htm

Kingsley
>
>
> 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
>>
>
>
>


-- 

Regards,

Kingsley Idehen	      
President & CEO 
OpenLink Software     
Web: http://www.openlinksw.com
Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca: kidehen

Received on Thursday, 25 February 2010 18:11:15 UTC