- From: Steve Harris <steve.harris@garlik.com>
- Date: Thu, 24 Mar 2011 05:35:30 +0000
- To: nathan@webr3.org
- Cc: RDF WG <public-rdf-wg@w3.org>
On 2011-03-23, at 16:22, Nathan wrote: > > Just wanted to capture something I don't think I've conveyed until now: > > Almost every developer I know, from enterprise to bedroom developers, work primarily with OO oriented languages, or key/value data structures in functional languages. > > The primary *huge* issue here, is that most people can't work with triples and graphs without special tooling. Not to mention that it's highly unfamiliar to them. > > Send an object with an id over the wire and people can use it, it's familiar, they "get it", send them a triple, and they're lost - even if they grok the graph and triple, they don't have the machinery to handle it often. This, I suspect is why SPARQL (either directly, or through an API) appear to be more popular than accessing RDF directly, in JavaScript. It gives you a way to turn RDF data into tables (list of lists, or lists of hashes) of data. Much, though far from all, of the data in the Linked Data cloud is available through public SPARQL endpoints. > This is pretty much the sole reason that every developer I know outside of the sem web community does not use RDF in any way, even though they like the concepts and would like "linked data". Sure, but if they did use RDF they'd be inside the sem web community by at least some definitions ;) - Steve -- Steve Harris, CTO, Garlik Limited 1-3 Halford Road, Richmond, TW10 6AW, UK +44 20 8439 8203 http://www.garlik.com/ Registered in England and Wales 535 7233 VAT # 849 0517 11 Registered office: Thames House, Portsmouth Road, Esher, Surrey, KT10 9AD
Received on Thursday, 24 March 2011 05:36:08 UTC