W3C home > Mailing lists > Public > public-lod@w3.org > July 2011

Re: A proposal for handling bulk data requests

From: Kingsley Idehen <kidehen@openlinksw.com>
Date: Mon, 11 Jul 2011 13:07:24 +0100
Message-ID: <4E1AE77C.1070507@openlinksw.com>
To: Jerven Bolleman <me@jerven.eu>
CC: public-lod@w3.org
On 7/11/11 12:17 PM, Jerven Bolleman wrote:
> Hi All,
>
> How does this interact with robots.txt and sitemaps? i.e. there is
> this extension to sitemaps from deri.
> http://sw.deri.org/2007/07/sitemapextension/scschema.xsd
> I don't know if any robot implements it.

Re. Michael's suggestion, the end product would be a dataset URL that's 
WebID protected. When the resource is generated the data set requester 
will be notified, which is where Twitter, G+, and other notification 
mechanisms come into play.

WebID negates the need for sitemaps, in this usecase. More importantly, 
WebID == APIKey++ and this is an example use case scenario that 
illuminates this reality.

Kingsley
> Regards,
> Jerven
>
> On Mon, Jul 11, 2011 at 12:58 PM, Kingsley Idehen
> <kidehen@openlinksw.com>  wrote:
>> On 7/11/11 11:39 AM, Michael Hausenblas wrote:
>>> Kingsley, Gio, All,
>>>
>>>
>>> An idea that arose out of a recent discussion with Juergen (in CC): how
>>> about providing a sort of 'bulk data request' facility for your SPARQL
>>> endpoints [1] [2] (as they are, I gather, the more popular ones on the WoD
>>> ;)?
>>>
>>> It could work as follows:
>>>
>>>
>>> 1. Someone uploads a VoID description [3] of the targeted datasets and
>>> provides an email, Twitter, G+ handle or a WebID
>>>
>>> 2. You could generate the 'customized' dataset internally in a very
>>> efficient manner.
>>>
>>> 3. Once available, the requester is notified by means of the provided
>>> back-channel from 1.
>> Yes, I like the fact that WebID, Twitter, and G+ are incorporated into the
>> suggestion.
>>
>>>
>>> I believe such a system in place would lower the crawling and bulk-query
>>> costs re bandwidth, etc. on your end, and opens up a business opportunity as
>>> well (think: WebID<->  Web Payments).
>> Yes, this is a nice example of DaaS (Data as a Service) pattern.
>>>
>>> What do you think?
>> Nice idea!
>>
>> Kingsley
>>> Cheers,
>>>     Michael
>>>
>>> [1] http://lod.openlinksw.com/sparql
>>> [2] http://sparql.sindice.com/
>>> [3] http://www.w3.org/TR/void/
>>>
>>> --
>>> Dr. Michael Hausenblas, Research Fellow
>>> LiDRC - Linked Data Research Centre
>>> DERI - Digital Enterprise Research Institute
>>> NUIG - National University of Ireland, Galway
>>> Ireland, Europe
>>> Tel. +353 91 495730
>>> http://linkeddata.deri.ie/
>>> http://sw-app.org/about.html
>>>
>>>
>>>
>>
>> --
>>
>> Regards,
>>
>> Kingsley Idehen
>> President&    CEO
>> OpenLink Software
>> Web: http://www.openlinksw.com
>> Weblog: http://www.openlinksw.com/blog/~kidehen
>> Twitter/Identi.ca: kidehen
>>
>>
>>
>>
>>
>>
>>
>
>


-- 

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 Monday, 11 July 2011 12:07:48 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 31 March 2013 14:24:34 UTC