Re: how to consume linked data

Hi Kjetil --

You wrote...

*I think there is a critical piece of technology that is missing in our
arsenal, namely a (free software) programming stack that makes a large group
of developers, who are likely to have little prior understanding of semweb,
to go "yeah, I can do that".*

How about being more ambitious?  In the above, change "a large group of *
developers*" to "a large group of *non-programmers*".

That would get you Social Media Meets Linked Data.

Here's step in that direction

  www.reengineeringllc.com/demo_agents/RDFQueryLangComparison1.agent

There's also a short paper


www.reengineeringllc.com/A_Wiki_for_Business_Rules_in_Open_Vocabulary_Executable_English.pdf

and the technology is online at the same site.

                            Cheers,   -- Adrian

Internet Business Logic
A Wiki and SOA Endpoint for Executable Open Vocabulary English over SQL and
RDF
Online at www.reengineeringllc.com    Shared use is free

Adrian Walker
Reengineering


On Fri, Sep 25, 2009 at 6:53 AM, Kjetil Kjernsmo <kjetil@kjernsmo.net>wrote:

> On Friday 25. September 2009 10:15:34 you wrote:
> > sorry if I sound negative, I reckon the semweb is a done deal now, the
> > many-eyeballs arrived.
>
> Thanks for asking the right questions, Danny, I believe it is critical for
> the success that someone does!
>
> > but - where should we take it?
>
> What I'd like to do with it, is to solve problems for people when combining
> data sets that are cannot be solved by conventional means, i.e. today the
> number of people who are interested in a particular combination of datasets
> goes down whereas the cost generally goes up, so it doesn't scale.
>
> I think there is a critical piece of technology that is missing in our
> arsenal, namely a (free software) programming stack that makes a large
> group of developers, who are likely to have little prior understanding of
> semweb, to go "yeah, I can do that".
>
> I think the work done by the Drupal folks is a right step in this
> direction, for the kind of stuff that people use a CMS for. But I think
> that we also need a stack, probably built around the MVC pattern, that can
> be used for more generic purposes.
>
> I haven't got anywhere with my ideas on this topic though...
>
>
> Kjetil
>
>