Comments for Wilbert's work blog

Comment on Meshing up a JISC e-learning project timeline, or: It’s Linked Data on the Web, stupid by Lorna’s JISC CETIS blog » When is Linked Data not Linked Data? - A summary of the debate

Tue, 16 Mar 2010 11:32:32 +0000

[...] Meshing up a JISC e-learning project timeline, or: It’s Linked Data on the Web, stupid - Wilbert Kraan, JISC CETIS, March 2009 [...]

Comment on Meshing up a JISC e-learning project timeline, or: It’s Linked Data on the Web, stupid by Lorna

Lorna — Mon, 15 Mar 2010 14:57:00 +0000

Thanks Wilbert, that’s very helpful indeed. More food for thought! I’ll come back to you about this via other channels shortly.

Comment on Meshing up a JISC e-learning project timeline, or: It’s Linked Data on the Web, stupid by Wilbert

Wilbert — Mon, 15 Mar 2010 14:53:06 +0000

SPARQL and RDF are a sine qua non of Linked Data, IMHO. You can keep the label, widen the definition out, and include other things, but then I’d have to find another label for what I’m interested in here.

What I’m arguing for here is that for data _providers_ should focus on nicely factored graphs and sensible URIs first, and worry about SPARQL endpoints later. From a _consumers_ point of view, though, SPARQL endpoints are the place where you start.

In that sense, there is also developer preference and experience. Tony Hirst is the grand wizard of Yahoo pipes. I don’t really get that stuff; it feels like trying to do calligraphy with boxing gloves on. And that’s before considering the fact that I’m reluctant to stick a lot of time in a proprietary platform.

On the other hand, I find it very easy and natural to think in rdf and sparql, but I guess not everyone’s brain is wired that way.

Not to fret, though: the simple meshup quickly goes from the results of a SPARQL query to formats more amenable to Tony’s mashups: CSV and Google spreadsheets. JSON and XML is just as easy.

Comment on Meshing up a JISC e-learning project timeline, or: It’s Linked Data on the Web, stupid by Lorna

Lorna — Mon, 15 Mar 2010 12:35:19 +0000

Well done, another very useful demo! I can only claim to vaguely grasp the technicalities here however I wonder if you could say a little more about SPARQL functionality (or not as the case may be!) I’ve been reading a lot of posts recently about the necessity, or not, of SPARQL for data to become Linked Data and I wondered what your opinion was? In a recent blog post Tony Hirst has suggested that SPARQL doesn’t cut it. What do you think? Can you have Linked Data without a SPARQL endpoint?

Comment on Linked Data meshup on a string by Wilbert’s work blog» Blog Archive » Meshing up a JISC e-learning project timeline, or: It’s Linked Data on the Web, stupid

Fri, 12 Mar 2010 14:49:51 +0000

[...] « Linked Data meshup on a string [...]

Comment on Linked Data meshup on a string by Sheila’s work blog » PRODing around Curriculum Design - what happened to content packaging?

Tue, 09 Mar 2010 10:46:08 +0000

[...] projects are using and identifying potential development areas. Wilbert Kraan has also recently blogged about his experiments around a linked data approach to information stored in PROD giving an [...]

Comment on Pinning enterprise architecture to the org chart by Mike Rollings

Mike Rollings — Sat, 06 Mar 2010 18:48:12 +0000

John,

I agree that we need to erase the divide between business and IT. We are all businesspeople. The more we remember that IT’s primary purpose is to enable business outcomes, the more healthy EA and IT will become.

Mike Rollings
Research Director
Burton Group

Comment on Linked Data meshup on a string by Kingsley Idehen

Kingsley Idehen — Sat, 27 Feb 2010 01:57:40 +0000

Nice demo! Here are some features you might not have realized about Virtuoso:

1. http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/VirtRdb2RDFViewsGeneration#OneClickLinkedDataGenerationAndDemployment — Wizard based Construction of RDF based Linked Data Views over SQL data that is ODBC or JDBC accessible

2. http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/VirtSponger — Cartridges/Drivers (via Sponger RDFizer Middleware) for generating RDF based Linked Data from a variety of Resource Types and/or Web Services

3. http://bit.ly/aK7N5R — Linked Data Page URL showing execution of SPARQL queries against remote SPARQL endpoints (URIBurner instance using DBpedia SPARQL endpoint)

4. http://bit.ly/bejHYl — URL exposing the distributed query above via our SPARQL Query By Example Tool

5. http://bit.ly/bJokvr — Basic Distributed SPARQL Queries e.g performing a SPARQL join across DBpedia and New York Times where crawling occurs via the Sponger Middleware that’s part of the Virtuoso SPARQL engine (URIBurner endpoint performing distributed join).

Kingsley

Comment on Linked Data meshup on a string by Sheila’s work blog » 2nd Linked Data Meetup London

Sheila’s work blog » 2nd Linked Data Meetup London — Fri, 26 Feb 2010 14:28:14 +0000

[...] of sectors about their ideas and approaches to linked data. My colleague Wilbert Kraan has also blogged about his experiments with some of our data about JISC funded [...]

Comment on Linked Data meshup on a string by Chris Wallace

Chris Wallace — Fri, 26 Feb 2010 08:19:06 +0000

Hi Wilbert, Nice work.

You may be interested in some work I did with the data set referred to in Richard Wallis’ article.

I’ve been playing with an RDF browser which infers the data model underlying a data set and provides some analytical browsing capabilities.

I described the application of the browser to the BIS dataset in a blog item (written the day of the Linked Data meeting which I had to miss)

http://kitwallace.posterous.com/viewing-and-reviewing-the-department-for-busi

Chris Wallace
UWE Bristol