4 ms·

Yes, but unlike XML, SGML can deal with HTML (arguably the most important markup application). I mean, XHTML didn't happen, so let's go back one step to XML's

Yes, but unlike XML, SGML can deal with HTML (arguably the most important markup application). I mean, XHTML didn't happen, so let's go back one step to XML's superset SGML which can do everything that XML can, and more. OTOH, the reaction of some people on the XML conference was like "what's this non-standard SGML thing?". Nevermind the fact that SGML is an ISO (United Nations) standard; doesn't get any more standard than that (with the possible exception of The Counsel of the Galactic Federation).

yellowapple 10y ago
"SGML can deal with HTML" Last I checked, that stopped being true as of HTML5.
- tannhaeuser 10y ago
  According to the analysis [1], the material issues that SGML has with HTML are - lexical issues; in particular, id/href values can be almost anything in HTML5, and are case-sensitive unlike other name-like tokens; note that while id/href values can be anything, they are however effectively constrained by other specification rules (eg. id values can't effectively contain quote characters because of attribute parsing rules) - script parsing is especially foobar'd (and injection-prone) in HTML (cruft from HTML3/HTML4 times) - HTML 5.1 constrains attributes on elements depending on the value of other attributes (possibly on parent element attributes), and also makes content model features dependent on parent attributes in some cases, which can't be described by an SGML DTD grammar (but then doesn't have to be described for parsing) YMMV but none of these things really matter that much in practice. [1]: http://sgmljs.net/docs/html5.html http://sgmljs.net/docs/html5.html
  - yuhong 10y ago
    There is also the issues with the EMBED tag, but plug-ins are dying.
yuhong 10y ago
That being said, even IE9+ can deal with XHTML now, but the entire document must confirm to XML rules and this might not be always acceptable.
- tannhaeuser 10y ago
  IE9? That was about the time I last did a site using XHTML (2010?) and two years before W3C ditched their XHTML efforts officially.
  - yuhong 10y ago
    *XHTML2

yellowapple 10y ago

"SGML can deal with HTML" Last I checked, that stopped being true as of HTML5.

tannhaeuser 10y ago
According to the analysis [1], the material issues that SGML has with HTML are - lexical issues; in particular, id/href values can be almost anything in HTML5, and are case-sensitive unlike other name-like tokens; note that while id/href values can be anything, they are however effectively constrained by other specification rules (eg. id values can't effectively contain quote characters because of attribute parsing rules) - script parsing is especially foobar'd (and injection-prone) in HTML (cruft from HTML3/HTML4 times) - HTML 5.1 constrains attributes on elements depending on the value of other attributes (possibly on parent element attributes), and also makes content model features dependent on parent attributes in some cases, which can't be described by an SGML DTD grammar (but then doesn't have to be described for parsing) YMMV but none of these things really matter that much in practice. [1]: http://sgmljs.net/docs/html5.html http://sgmljs.net/docs/html5.html
- yuhong 10y ago
  There is also the issues with the EMBED tag, but plug-ins are dying.

yuhong 10y ago

That being said, even IE9+ can deal with XHTML now, but the entire document must confirm to XML rules and this might not be always acceptable.

tannhaeuser 10y ago
IE9? That was about the time I last did a site using XHTML (2010?) and two years before W3C ditched their XHTML efforts officially.
- yuhong 10y ago
  *XHTML2