4 ms·
When rococode says 'It turns out though, that improvements in NLP mean there is still hope for a slightly different incarnation of the Semantic Web.' maybe the
by bryanrasmussen 7y ago
When rococode says 'It turns out though, that improvements in NLP mean there is still hope for a slightly different incarnation of the Semantic Web.'
maybe the reason it failed is just another example of metacrap https://people.well.com/user/doctorow/metacrap.htm https://people.well.com/user/doctorow/metacrap.htm
aside from that my take is that it failed at two different points - first point original RDF specs and push to add RDF, second point SPARQL.
First point reasons for failure (in no particular order) -
1. The RDF community were sort of jerks - I can't count how many times people came on XML-DEV or other communities talking about the difficulties of representing RDF in XML and were dismissed with haughty versions of you don't need XML to represent RDF. This was not the most winning attitude to get new people onboard.
2. RDF is hard to represent in XML and almost every tutorial that showed you how to work with RDF did it in context of XML. At the time XML was the runaway train of standards success, and it seemed like the idea was to attach the RDF car to it in any way they could. But the two things did not really attach well.
3. Web development then, as now, has been about having to deal with lots of changes all the time, anything that requires a steep learning curve, has no immediate benefit, and is hard to do right is at a significant disadvantage.
4. About the syntax and mapping of RDF to XML, at the time I was building a product that was supposed to handle media transformations between many XML inputs and RDF was a problem for me. I remember another of the commonly said things at the time was you don't need to worry about writing RDF because your tools will do all that for you, well I was writing the tools and I hated it.
So for these various reasons, and the metacrap one, RDF did not take off.
SPARQL not succeeding was actually somewhat surprising to me, when it first came out I thought it had potential, but I did think it was going against some things that had quite the traction at the time -
1. I would often see tutorials with these Sparql/Linked Data URIS had all the search query in them and looked awful, this was when everyone was very excited about REST and making theirs urls meaningful to humans - the examples given just looked bad in relation to the aesthetic current at the time.
2. RDF was already thought of as a failed technology - once a technology fails it is really hard to get management to invest in a second coming.
3. The bloom was off the rose for W3C at the time, this was when WHATWG was being formed, another strike against from a managerial standpoint I'd think.
4. Maybe the strains of Web Development are such that it cannot handle more than one big standard arriving at a time - this is just a feeling on my part but SPARQL and HTML5 were coming at about the same time (or is my recollection off - I think both started in 2008-9) maybe there's just too much work for people to do that.
Ok, these are of course various expressions of my personal feelings as to why it didn't work, but given our inability to really test the issue I suppose the same will apply to anyone else's ideas on the matter.