Slashdot Mirror


W3C Considering An HTML 5

An anonymous reader writes "When the decision was initially made to move in the direction of XHTML, instead of a new version of HTML proper, it seemed like a good idea. Years later and the widespread adoption of CSS (among other things) has proven that things don't always develop the way we expect. As a result, HTML 5 has been revived by the W3C. After some lobbying and continued work by the Web Hypertext Application Technology Working Group, the old web markup language is getting an official face-lift. A post to the Webforefront blog explains the history behind the initial decision to move to XHTML, and why things are so different in the here and now."

1 of 414 comments (clear)

  1. One thing that's always irritated me about XML... by jez9999 · · Score: 0, Offtopic

    ... is that its tags are case-sensitive. This doesn't make any friggin' sense. I've never seen a case where they define 2 tags named identically but cased differently, and indeed it would be silly and confusing, yet XML behaves as if this is the case. XHTML inherits this limitation. I like my HTML tags in uppercase, damnit, to make them more obviously separated from the content! Are XML parsers too lazy to do something like "lc(string1) == lc(string2)"?