Re: Can we afford to offer SPARQL endpoints when we are successful? (Was "linked data hosted somewhere")

On Thu, Nov 27, 2008 at 2:33 PM, Peter Ansell <ansell.peter@gmail.com>wrote:

> 2008/11/27 Richard Cyganiak <richard@cyganiak.de>
>
>>
>> Hugh,
>>
>> Here's what I think we will see in the area of RDF publishing in a few
>> years:
>>
>> - those query capabilities are described in RDF and hence can be invoked
>> by tools such as SQUIN/SemWebClient to answer certain queries efficiently
>>
>
> I still don't understand what SQUIN etc have that goes above
> Jena/Sesame/SemWeb etc which can do this URI resolution with very little
> programming knowledge in custom applications.
>

True, jena/sesame does everything that SQUIN entails to do. However, SQUIN
is oriented to the "web2.0" developers. How is a php/ror web developer going
to interact with the web of data and make some kind of semantic-linked data
mashup over a night? SQUIN will let them do this. No need of having jena,
learning jena, etc. Make it simple! If it is not simple, then developers are
not going to use it.