QUOTE(Sn0wm4n @ 17 Jul, 2008 - 08:48 AM)

I'm reading this book and I don't understand why version 1.0 would be the baseline if there is a version 1.1 out. I understand why 2.0 isn't becuase it's in the working draft form. Now this book is like 4 years old so please tell me if this has changed or this is wrong but please me why they would use an older version. The passage from the book is below...
Neither XHTML 1.0 nor 1.1 are really better than HTML 4.01 at the moment since Internet Explorer does not support XHTML. That said, the most useful feature that XHTML 1.1 has over XHTML 1.0 is XHTML Ruby.
Unfortunately, the only browser that supports XHTML Ruby (Internet Explorer) is also the only browser that lacks support for XHTML. (Internet Explorer implements Ruby elements as proprietary HTML elements. I’m guessing that they implemented it since one of their employees wrote the CSS3 Ruby spec.) It looks like Mozilla is doing some work on Ruby again, but I don’t see it being implemented any time soon. I can’t really blame anyone for not implementing it though; the basis for XHTML Ruby is CSS3 Ruby which, IMHO, is very poorly written.
So, the point is that the most useful feature of XHTML 1.1 is currently useless and, thus, XHTML 1.1 has no notable advantages over XHTML 1.0. Also: XHTML 1.1 has also reverted back to W3C Working Draft status (from W3C Recommendation status, no less) so it’s no longer part of a final specification; the HTML 5 Working Group has declared that HTML 5 is the successor to XHTML 1.0 (i.e., XHTML 1.0 advances to “XHTML 5”, not XHTML 1.1 or 2.0); real XHTML can’t be used on the Web, generally, thanks to Microsoft; and the “HTML‐compatible” features of HTMLized XHTML are removed in XHTML 1.0 (i.e., Appendix C). Thus, you have few reasons to use 1.1.