2 ms·
When I got exposed to semantic web probably 4 years ago, I realized what a huge mistake it was/is. My take is that it is a bunch of ideas to make it easier for
by programminggeek 12y ago
When I got exposed to semantic web probably 4 years ago, I realized what a huge mistake it was/is.
My take is that it is a bunch of ideas to make it easier for search engines to crawl and use your data about all kinds of things. On one hand, that is great.
However, the huge problem with using it is that you end up creating your own search engine to crawl data sources to do anything useful. That is to say, you have to crawl the data, store it somewhere, and then build up your own systems for querying or doing anything useful with the data.
The use case many people have is that they want to use and API to get some particular bit of data out and that's it. Like, say you want to do a search for a list of tweets on Twitter with the hashtag #HackerNews. The sane thing to do is to be able to hit a twitter api endpoint and have it send you back a list of tweets with that hash tag.
Now, imagine if instead you had to index all of twitter and filter yourself for tweets with #HackerNews in it. Is that better for that particular use case? No, it sucks.
There are certainly cases where you DO want to crawl data and do your own data analysis on it. But, that is a much more limited use case for many developers and there isn't as much value in that as people seem to believe.
A better solution would be something like REST with HATEOS on a much larger scale. You'd be able to index things nicely, but still have the benefits of smarter API calls.
Unfortunately, I don't see this happening anytime soon, despite the interesting things you could build with it.
- j13z 12y agoI agree, the crawling / indexing problems you describe are definitely true for Linked Data. But there are still other use cases for semantic web technology. > The use case many people have is that they want to use and API to get some particular bit of data out and that's it. In theory, that's what SPARQL and SPARQL endpoints are for. Plus you get things like federated queries and an open data model (RDF), that allows to combine multiple data sources without "wrapping" schemas. But well, this is kind of utopia and yes, I doubt it will ever be "a thing".