As web standards advocates, many of us participate in numerous online communities such as mailing lists, forums, newsgroups and even blogs (both our own and comments on others). In these communities, we often encounter beginners who are either just starting out with HTML, or have been doing HTML for a while, but are new to the concept of developing with standards.
Invariably, such beginners face the eternal question of HTML or XHTML; and today, I intend to answer this question (as it applies to beginners) once and for all. For experienced users, the
The XHTML 2 specification isn't finished, but it already has many advantages over XHTML 1, including a greater structural richness that will make it more viable than its predecessor as an editorial format to serve as the central schema for a single-source publishing system. Without waiting for browser support of the new user interface features in XHTML 2, people who do large- or small-scale publishing can start to use these new features now.
About a year ago, an industry standards group asked me to do a presentation on how XHTML 2 might be useful to
As web standards advocates, many of us participate in numerous online communities such as mailing lists, forums, newsgroups and even blogs (both our own and comments on others). In these communities, we often encounter beginners who are either just starting out with HTML, or have been doing HTML for a while, but are new to the concept of developing with standards.
Invariably, such beginners face the eternal question of HTML or XHTML; and today, I intend to answer this question (as it applies to beginners) once and for all. For experienced users, the
RSS/XML