4 ms·
I was replying to another commenter, but they deleted their post. I still think my response is legitimate, and I'd like to discuss. I'm including the post and m
by echelon 6y ago
I was replying to another commenter, but they deleted their post. I still think my response is legitimate, and I'd like to discuss. I'm including the post and my response to it:
> This might be an unpopular opinion, but the Semantic Web was yet another idea that only could've come from Architecture Astronauts. Neither web developers nor web users wanted or needed it, but the Astronauts just kept pushing forward, with no support whatsoever, until people with actual skin in the game of the future of the Web got fed up and sidelined the W3C in favor of WHATWG/HTML5.
> When the Architecture Astronauts produce a product no one wants/needs at a big megacorp like Microsoft, it's easy to make fun of them, but for whatever reason when it happens in an open-source environment or in academia, people are a lot more likely to lament "Oh, why couldn't they understand?", which has it backwards: it's your job to understand them, and in your arrogance you deliberately didn't do that.
The Semantic Web flew in the face of enterprises like Google. It posited to put all information into a queryable ontology. With a rich and expressive grammar, who needs Google's algorithms to rank anything? All you need to do is ingest and you can weight the edges based on who else consumes them.
Google actually knee-capped the web with the WHATWG's focus on less semantic documents. The platforms with their army of engineers are what did the technology in.
If the Semantic Web had a chance to grow before the giants of tech emerged, we might be looking at a vastly superior internet today.
- baron_harkonnen 6y ago> If the Semantic Web had a chance to grow before the giants of tech emerged, we might be looking at a vastly superior internet today. I worked pretty closely with people doing a lot of semantic web work in the 2006ish era, before Google and ML dominated tech. Even then it was nearly impossible to find a single, useful example of the semantic web in action. The reasoner a la something like OWL is the true heart of the semantic web, but that never got solved at the scale necessary for the web. For any practical problem or even interesting side projects semantic web technologies didn't offer anything that you couldn't build better using existing tools. People made RDF data stores because they wanted to use RDF, but I don't recall any interesting demos of semantic reasoners.
- lmm 6y ago> Google actually knee-capped the web with the WHATWG's focus on less semantic documents. The platforms with their army of engineers are what did the technology in. Nah. Those platforms had years or decades to make their overengineered crap work, and they never could. XHTML2.0 was never finished, all those RDF ontologies never got anywhere, and all the semantic search engines couldn't find anything. Google made a search engine that worked better than any other precisely because it ignored all the semantic bollocks, and eventually, after the web had stagnated for years by focusing on said semantic nonsense, the WHATWG formed to standardise some HTML that websites and users actually wanted. The person you were replying to had the right of it. If the semantic web was actually any good, it would've produced a better search engine than Google.
- nwmcsween 6y agoYep instead of xlst we now have a dozen javascript or server side solutions. HTML5 was pragmatic but to a fault.
- lmm 6y ago> instead of xlst we now have a dozen javascript or server side solutions. And not one of them is harder to work with than XSLT. I'm all for declarative transformations in theory, but XSLT just sucks so bad if you actually try to use it.
- nwmcsween 6y agoIt used to be a mess rendering a site to pdf, it's much better but still isn't great if you look over the issues on various HTML -> PDF projects. The issue with HTML5 is it threw everything away for pragmatism but in doing so we have HTML and javascript, a lot of javascript. I also really didn't mind xlst
- lumost 6y agoScalable rigid ontologies are hard to the point of being impossible. Even tasks well suited to ontologies such as Question Answering see better results from non-ontological approaches.
- deleted 6y ago[deleted]
- ptsneves 6y agoI am not knowlegeable in semantic web but isn't a hashtag a form of semantic categorizing of data? If so the hashtag movement is very recent. I always wondered who the hastags serve: humans or machines? I think it was machines firstly but then it got appropriated by social dynamics of people and business.
- echelon 6y agoThe semantic web was much richer. You could build an ontology in RDF [1] or OWL [2] and link the grammars together. FOAF [3] was a means of describing your friends and social connections, and it allowed rich annotation. No tools were ever built around this because by the time it started taking off, Facebook and MySpace were already a thing. The great thing about these technologies is that the graph is public and you could write tools to ingest, export, and exchange the information. We never got to that, though. The technology was centered around graphs and triple stores, allowing you to apply subject-predicate labels to anything. The URI became a central node, document, and ontology identification scheme. There were languages like SPARQL for querying rich triplestore databases, but they never really took off. Again, Google and Facebook were already huge by the time these started to mature. If you think the promise of blockchain is exciting, you should take a look at what the Semantic Web could have been... [1] https://www.w3.org/TR/rdf-primer/ https://www.w3.org/TR/rdf-primer/ [2] https://www.w3.org/TR/owl2-primer/ https://www.w3.org/TR/owl2-primer/ [3] http://www.foaf-project.org/ http://www.foaf-project.org/
- bawolff 6y ago> The semantic web was much richer Which is probably why it failed. Richer means more complex, means higher effort, means harder to justify the immediate effort. It also means more difficult to figure out which sources are trustworthy because it all gets mangled together. The success of google is not that they are good at indexing, but good at ranking. People are constantly trying to game the search engine system. The naive model of querying a semantic web builtup doesn't mesh well with a certain percent of participants being malicious. And that's excluding the whole problem that scaling searching large complex graph databases is basically an unsolved problem
- jolux 6y agoWHATWG is also somewhat less subtly a vehicle for Google to turn Chrome into the only functioning web browser.
- minimuffins 6y ago> The Semantic Web flew in the face of enterprises like Google. This is a good analysis. Oftentimes the answer to why some technology succeeds or fails is more than just purely technical. It can be really useful to think in these kinds of materialist terms ("Who benefits?") to get a fuller picture.
- wwweston 6y agoThe irony here is that Google was built on the light semantics of the hyperlink: the anchor tag is the semantic web, giving you information that a server-side image map or Java applet or Flash movie or JS-driven navigation couldn't reliably identify without putting a hell of a lot more effort into your crawler. There were probably always limits to how widely useful (or adopted) a single coherent set of resource definitions / markup conventions could have been, but for all the early value demonstrated by Google itself it sure seems like there really wasn't enough thought about the value proposition. > Neither web developers nor web users wanted or needed it, Users want search, first without having to put too much thought into modeling what they're looking for, then maybe with some additional options with an intuition or understanding of how results might be improved. They might not know how the semantic web could help with that any more than they know how Ruby helps their application exist, and it makes about as much sense to say users don't care about the semantic web as they don't care about Ruby. Both are potential waiting to be realized into an experience. Developers, on the other hand, don't have anywhere near as good an excuse.
- evrydayhustling 6y ago> light semantics of the hyperlink: the anchor tag is the semantic web, giving you information that a server-side image map or Java applet or Flash movie or JS-driven navigation couldn't reliably identify This, 100x. Complex and precise ontologies don't survive a distributed environment because communication is competitive. Publishers don't seek to describe themselves "accurately" (as if everyone could agree what that means), they seek to attract a certain type of attention in maximum quantities. The protocols that survive that policy framework are those that "carry their own weight" for both listeners (by compressing information that would be hard to get) and publishers (by allowing sufficient expression to pursue selfish ends without lying). Hyperlinks nail this trade off (at least well enough that pagerank successfully trims the noise). But Semantic Web gave little incentive for publishers to represent themselves, accurately or at all.
- xnx 6y agoGreat point. Individual publishers are to be trusted so little in describing their own content that Google completely ignores the keywords meta tag (and also description now I think).
- detaro 6y agoI'm quite sceptical that "a queryable ontology. With a rich and expressive grammar" would be so obviously easy to use and great that it threatened Google, rather than Google being a frontend for said ontology (that you still need to crawl first to use!). And indeed, what remains of semantic-web like data is massively pushed by Google today, because it makes it a easier for them to provide results based on that - and if you want to convince someone to add it to a website in a commercial setting, "it helps Google understand our site" is the primary argument that sticks (even though it also helps others parse sites). Which IMHO points to the main problem: Publishing semantic data is work, and had no clear value proposition you could sell businesses on, and it ran out of steam before someone made a convincing one. Niches that see the need for such data publishing still are willing to use this stuff or alternatives, but for the general majority of publishers it isn't there, or actively seen as a negative. It also didn't help that IMHO the focus was to much on what was theoretically possible, but not on making it actually easy to use, which made even more devs ignore it or build alternatives because the entry hurdle is steep. Plenty APIs could build on semantic web tech, but they don't because a custom REST API is typically just easier to do and thus more familiar. (Despite semantic tech having the groundworks for lots of what's seen as new-ish trends like API generators/machine readable API docs/...)
- jcranmer 6y ago> Google actually knee-capped the web with the WHATWG's focus on less semantic documents. There's one teensy problem with your thesis: Google came late to the WHATWG. The WHATWG started initially as a joint Mozilla-Opera project [1] to basically standardize what you had to do to parse the crap that passes for webpages (including de-facto standard behavior for DOM at the time). At the same time, it also included a variety of speculative features to push the capabilities of the web forward: <canvas>, <audio>, <video>, not to mention Web Forms (eventually morphed into all the nice, new <input> types). It even had semantic elements: <section>/<header>/<footer> originate from WHATWG, after all. Not to mention microdata, too. Google Chrome doesn't come out until 2008. XHTML 2.0 is put out of its misery in 2009, but that the WHATWG was now the driving force in HTML innovation was clear by 2006 or 2007, by virtue of all browser vendors focusing on WHATWG HTML support and not W3C XHTML 2.0. The W3C tries to regain relevance by staring from WHATWG HTML instead of XHTML for HTML 5 in 2007. [1] Apple was also involved very near the beginning, but I don't know to what degree it was involved.
- Karrot_Kream 6y ago> Google Chrome doesn't come out until 2008 Oh of course, Google didn't have a horse in the race for the application web at all until 2008. Except wait, they had released GMail in 2004 and Google Maps in 2005. In fact, WHATWG made frequent references to GMail and Google Maps as examples of the application web and deficiencies that W3C was not addressing in its XHTML standard. Then Ian Hickson, the main editor behind the WHATWG HTML5 standardization process, went to Google. One of my favorite quotes from Hickson about the whole process (as I noted in a sibling comment): "The Web is, and should be, driven by technical merit, not consensus. The W3C pretends otherwise, and wastes a lot of time for it. The WHATWG does not." This says a lot both about the outlook of the WHATWG of the time and the way the development community of the time saw web corporations at the time. And now we have 2 major browsers as of this writing. It's funny how much flak Berners-Lee gets over his acquiescence to DRM and yet the WHATWG discussions of the time are completely glossed over. I was fairly young when the WHATWG and W3C power struggle occurred, but it was a great lesson for me as a teenage programmer in the power of value capture.
- nostrademons 6y ago[Source/disclaimer: I was working on a number of these markup parsing & unstructured data mining projects at Google in the 2009-2014 timeframe, and also wrote an HTML5 parser with the cooperation of the WHATWG. I left for about 6 years during the time period when Google began to be seen as this evil goliath, but I'm back now. My views are my own and don't represent my employer.] You've got the cause & effect backwards. Google invested heavily in existing standards-based microformats (RDF, schema.org, OpenSocial, various rel= standards) before ultimately concluding that web developers cannot be trusted to get markup right, and most don't want to do it in the first place. It was only after this failure that we threw out all the markup parsing and went to machine-learning & algorithmic approaches, and then eventually to just owning a bunch of the content platforms where people write content. Customer desires - in the form of what people will actually do, not what they claim they want to do - ultimately decide the structure of a market. If a large number of competing publishers all decide they want to publish content and users divide their attention evenly among them, you get open standards, protocols, and aggregators. If users decide they all want to view the most popular content, then the dominant firms become more dominant, you get silos and walled gardens (and eventually paywalls), and power shifts from an open ecosystem to a few dominant players. Google was built on the open web and embraced the philosophy of it for longer than any other major company, but people there are very pragmatic. When it became clear that there would be a few dominant companies, the priority shifted to being one of them rather than investing in (and getting screwed by) an open ecosystem that was disappearing.
- Karrot_Kream 6y ago> You've got the cause & effect backwards. Google invested heavily in existing standards-based microformats (RDF, schema.org, OpenSocial, various rel= standards) Mm yes, much like XMPP and Google Chat/Facebook. Pay lip-service to a standard when you _don't_ own the mindshare, drive mindshare to you, then sunset the standard for your implementation when you have the mindshare. An innocent play, for sure. That said, of course Google was not a founding member of WHATWG. The reason the association is so stubbornly believed is because WHATWG's Ian Hickson went to Google. At the risk of an aside, one of my "favorite" Ian Hickson quotes goes as follows: "The Web is, and should be, driven by technical merit, not consensus. The W3C pretends otherwise, and wastes a lot of time for it. The WHATWG does not." I suspect in today's world this phrase would be out of place. But of course, this was a more innocent time. > before ultimately concluding that web developers cannot be trusted to get markup right, and most don't want to do it in the first place I think a massive conflict of interest needs to be disclosed here: ad revenue. Microdata and schema.org was a change from the original promise of the Semantic Web. The Semantic Web was about exposing semantic data on pages so that search engines and other data processors could compete on discovery. Microdata and schema.org took a lighter-weight approach that _specifically focused_ on fields relevant to incumbent search engines, a la Google. The legacy lives on as Microdata today is only used as a form of SEO ranking boosting. > Customer desires - in the form of what people will actually do, not what they claim they want to do - ultimately decide the structure of a market I'm going to disagree here. Customer desires dictated nothing of the sort. (From what I remember (though I was young at the time), the general public really didn't have much desire or education about the net or the web as a whole at the time.) The big web companies started to understand the value of data. Even a decade ago, the FAANG equivalents (Google, LinkedIn, Microsoft, et al) were already very open internally about how much of their value was in their data or in their network. It wasn't customer desire that drove any of this, it was monetary desire. > When it became clear that there would be a few dominant companies, the priority shifted to being one of them rather than investing in (and getting screwed by) an open ecosystem that was disappearing. What a sad sentiment. I disagree. This reads like something out of Machiavelli's The Prince.