Re: Semantic Web pneumonia and the Linked Data flu (was: Can we lower the LD entry cost please (part 1)?)

Andreas, Yves,

> it would be nice to create some remote voiD buttler service for those
> who don't want to spend too mutch time to create their own
> descriptions.

Isn't that what [1] gives you?

Cheers,
      Michael

[1] 
http://linkeddata.uriburner.com/about/html/http://twitter.com/kidehen%23Data
set

-- 
Dr. Michael Hausenblas
DERI - Digital Enterprise Research Institute
National University of Ireland, Lower Dangan,
Galway, Ireland, Europe
Tel. +353 91 495730
http://sw-app.org/about.html


> From: Andreas Langegger <al@jku.at>
> Date: Mon, 9 Feb 2009 12:33:39 +0100
> To: Yves Raimond <yves.raimond@gmail.com>
> Cc: Linked Data community <public-lod@w3.org>
> Subject: Re: Semantic Web pneumonia and the Linked Data flu (was: Can we lower
> the   LD entry cost please (part 1)?)
> Resent-From: Linked Data community <public-lod@w3.org>
> Resent-Date: Mon, 09 Feb 2009 11:34:24 +0000
> 
> 
> Hi Yves,
> 
> On Feb 9, 2009, at 11:40 AM, Yves Raimond wrote:
>> the beginning! If someone really wants a smallish search engine on top
>> of some dataset, wrapping a SPARQL query, or a call to the web service
>> that the dataset wraps should be enough. I don't see how the data
> 
> +1 ...however, as long as standard SPARQL has no fulltext search and
> aggregates, this might not always be possible.
> If you want to fetch more detailed statistics (what I can do with
> RDFStats), you really need count(*) at least if you want to do it
> remotely!
> 
>> publisher is required for achieving that aim. The same thing holds for
>> voiD and other technologies. Detailed statistics are available on most
>> dataset homepages, which (I think) provides enough data to write a
>> good enough voiD description.
> 
> it would be nice to create some remote voiD buttler service for those
> who don't want to spend too mutch time to create their own
> descriptions. THe void buttler will try to find out as many
> information as possible remotely. Many things could actually be done
> remotely (e.g. finding dc:subject/skos:subject terms), the remaining
> information could be entered by the publisher in some form inputs.
> 
>> 
>> 
>> To sum up, I am just increasingly concerned that we are building
>> requirements on top of requirements for the sake of lowering a  "LD
>> entry cost", whereas I have the feeling that this cost is really
>> higher and higher... And all that doesn't make the data more linked
>> :-)
> 
> I still very much like the idea of LOD, I like the projects happening
> and people being enthusiastic. But it is driven by people who like to
> do this, who like to sit down and setup tools, etc. So, for the broad
> to adopt, it must be as easy as possible and I think Yves raised an
> important point.
> 
> AndyL
> 
>> 
>> 
>> Cheers!
>> y
>> 
> 
> 
> http://www.langegger.at
> ----------------------------------------------------------------------
> Dipl.-Ing.(FH) Andreas Langegger
> Institute for Applied Knowledge Processing
> Johannes Kepler University Linz
> A-4040 Linz, Altenberger Straße 69
> 
> 
> 
> 
>

Received on Monday, 9 February 2009 11:44:44 UTC