3 ms·
They killed momentum on XHTML, which included reusable modularization and components. Inclusion of semantic web / structured RDF graph data was an objective, an
by echelon 4y ago
They killed momentum on XHTML, which included reusable modularization and components. Inclusion of semantic web / structured RDF graph data was an objective, and this all got pushed by the wayside.
Strict, structured data could have posed a threat to Google by enabling other search engines to more easily build fact-based competitors and crawl the web of rich data. The decentralized nature of OWL/RDF would have pushed the web closer to P2P aggregation (think RSS, FOAF, pingback...)
The web could have been less Facebook-y, less Google-y, more Napster, more GPT-3 if XHTML had won.
- shadowgovt 4y agoThat last assertion is heavy speculation. Why are we assuming that, had XHTML been the dominant infrastructure, Facebook and Google wouldn't still be the best at leveraging it? And if anything, Google desperately did and does want people to semantically annotate data. They're extremely confident in their ability to be the best at organizing it, and well-annotated clean data is a huge benefit to them.
- goto11 4y agoRDF is independent of (X)HTML and W3C kept control of RDF and related standards. It is true that RDF have failed to live up to its promise, but this have nothing to do with WHATWG.
- bawolff 4y agoThe RDF vision (where every website authors their own rdf graph in an open world sort of way, which web spiders search in a unified fashion) has tons of problems that its advocates refuse to acknowledge. Most notably lack of incentives to participate, complex authoring burden and poor scalability of graph querying. The only time rdf has had success is when there is only an extremely limited vocabulary allowed (xmp, certain other metadata standards) or when the ecosystem is closed so its just one site or group making the rdf (e.g. wikidata) It was never a threat to google because it was never going to win.
- ShroudedNight 4y agoDid the people driving the semantic web ever really get traction on the taxonomy problem? I vaguely remember a lot of hand-waving about semantic ontologies, but the mechanics to actual reconcile the widely divergent labels humans inevitably produce always seemed to be someone else's problem.
- mike_hearn 4y agoWhat killed XHTML was the lack of backwards compatibility and especially the first-mover problem with embedding and the ads ecosystem. Namely, making a large production website fully validate was very hard, yielded zero ROI, and if anything went even slightly wrong such that invalid XML was emitted that would create a site outage that you couldn't easily detect server side. That's a bitter pill to swallow even as is, but now throw in the common practice of mixing in markup from third parties for ads, social buttons, login forms and other things and now you can have a major site outage caused at random by third parties, which, again, cannot be detected server side. As for RDF, GPT-3 is sort of the ultimate repudiation to that whole line of AI research. GPT-3 doesn't care about structured data at all, it can't even use it any better than a human would.
- tannhaeuser 4y agoDisagree. HTML, until HTML 4.01 published 1999, was formulated as an SGML vocabulary. Then, starting in 1997, W3C (technically, the SGML Extended Review Board in cooperation with ISO) "went meta" and created XML as an SGML subset in anticipation of a wealth of new vocabularies on browsers to be supported, of which SVG and MathML made it. Today, these vocabularies are integrated into HTML, with HTML rather than XML parsing rules (for example, element names are treated case-insensitive). HTML itself still uses tag inference and attribute shortforms that are only part of SGML but not the XML subset of SGML. Basically, the multi-year detour of creating XML was not worth it for the web since everything XML could do was by definition possible using SGML as well, it being a strict superset of XML, despite XML being hugely successful in enterprise computing and the publishing industry, and most HNers only knowing XML. What XML (XHTML2) was onto, however, was a completely unrealistic attempt to redefine browser behavior and vocabulary, with no buy-in from browser vendors (except Opera?), and with things such as XForms and wildly unproven RDF/SPARQL stuff. Ian Hickson was right in 2004 to fork HTML; browser vendors had no alternative.