#20459
XHTML is the standard markup language for web documents and the successor to HTML 4. Library projects must be authored in structural XHTML 1.0 Transitional. The following topics provide all the information you need to create well-formed XHTML pages that validate and are accessible, and/or to convert old HTML pages to valid, well-formed, accessible XHTML.
New York Public Library (2001). Design>Web Design>XHTML
#29327
Put XHTML 1.0 Strict and Transitional to Work 
As its name suggests, XHTML--which is considered the successor to HTML 4--is a combination of HTML and XML. By combining the power of XML and HTML, XHTML makes Web content more accessible to devices such as phones, handhelds, and televisions. XHTML 1.0 is broken up into what the W3C refers to as three flavors: Strict, Transitional, and Frameset. In this article, I focus on the two most useful, Strict and Transitional.
Morton, Shawn. TechRepublic (2003). Articles>Web Design>Standards>XHTML
#20263
The W3C’s XHTML language is intended to bridge the web’s past (HTML) and future (XML). Shall we cross this bridge, now that we’ve come to it? Or is XHTML more trouble than it’s worth? Peter-Paul Koch puts forth the pros and cons.
Koch, Peter-Paul. List Apart, A (2000). Design>Web Design>XML>XHTML
#27749
Rescue Terrible HTML with TagSoup
XHTML is a friendly enough format for parsing and screen-scraping, but the Web still has a lot of messy HTML out there. In this tip Uche Ogbuji demonstrates the use of TagSoup to turn just about any HTML into neat XHTML.
Ogbuji, Uche. IBM (2006). Design>Web Design>HTML>XHTML
#28241
The Lesser (or Badged) Standardista will include badges on their site to indicate which level of automated testing their site has passed, whereas the Greater (or Smug) Standardista frowns on the use of badges, and insists on double-checking every checkpoint manually.
Pickard, Jack. List Apart, A (2006). Design>Web Design>Standards>XHTML
#21172
Streamlining with Web Standards
Save time, money, blood, sweat, and tears by rebuilding your old-school site with standards-friendly CSS and XHTML.
Penhaligon, Greg. Webmonkey (2003). Design>Web Design>CSS>XHTML
#30650
The Trouble with Web Standards
You may mistrust web standards because of bad experiences with buggy browsers. Or you might have converted a site from HTML to XHTML, only to discover that their layouts suddenly looked different in standards-compliant browsers. Don't give in to the dark side! Web standards are here to stay.
Zeldman, Jeffrey. Creative Pro (2007). Articles>Web Design>Standards>XHTML
#13671
To Use or Not to Use: An XHTML Roadmap for Designers
The problem with XHTML 1.0 isn't a matter of strength, or of importance. XHTML is both strong and important--and not just for markup snobs and hardcore developers. It's not that XHTML 1.0 has a particularly high learning curve. It doesn't--in fact, it's quite easy to learn. And, it's not that XHTML 1.0 doesn't display in browsers both current and past. When written with awareness of cross-browser considerations--just as with HTML, it does. The problem lies in the fact that XHTML is, quite simply, misunderstood.
Holzschlag, Molly E. Digital Web Magazine (2001). Design>Web Design>Standards>XHTML
#20677
Transitional Layouts in (X)HTML and CSS: An Interview with Eric A. Meyer
In a pivotal user test a couple years ago we found out one of the secrets of great web sites: they inspire confidence in users. This article explores how to measure it and use it to your advantage.
Porter, Joshua. User Interface Engineering (2003). Articles>Web Design>XHTML
#19632
Using XHTML/CSS for an Effective Search Engine Optimization Campaign
We’re going to be focusing entirely on the benefits of using XHTML and CSS to show you how to improve the readability of your code for search engine spiders, maintain a good content-to-code ratio without going beyond file-size and word-count limits, and how to use CSS to mimic common image effects.
Olejniczak, Brandon. List Apart, A (2003). Design>Web Design>Standards>XHTML
#29986
Microformats is a term used to describe the storage of information using simple markup variations within existing markup languages. To a certain extent, microformats describes a methodology or philosophy, and comprises a set of design principles. Microformats is not a new language. It is usually a permutation of XHTML. The philosophy of microformats involves storing data in human-readable formats which are also machine-readable, but the emphasis is on the humans! Information tends to be visible, rather than hidden metadata.
Self, Tony. HyperWrite (2004). Articles>Web Design>Information Design>XHTML
#20461
Web Developer Foundations: Using XHTML
Web Developer Foundations provides an introduction to the skills and concepts that web developers need to know. The resources at this site are intended to aid you as you work through a related textbook.
Felke, Terry A. Scott-Jones Publishing (2002). Design>Web Design>XHTML
#29328
What XHTML Means for Wireless Development
XHTML is emerging as the content-authoring language for wireless development, so you'll need to have a strong grasp of XHTMLMod and XHTML Basic. See what you need to know about the changing wireless development landscape.
Gupta, Puneet. TechRepublic (2003). Design>Web Design>Wireless Web>XHTML
#21578
#20513
A collection of the valid tags and attributes within XHTML 'strict' encoding, with examples.
#20393
XHTML 1.0: Marking Up a New Dawn
Still writing your documents in HTML? If you are, you're not complying with current standards. On January 26, 2000, XHTML 1.0 became a recommendation by the World Wide Web Consortium (W3C). HTML, according to the W3C, is no longer the Web markup standard. Instead, XHTML 1.0 has replaced our old favorite, marking up the dawn of a new and exciting time in communications technology.
#28348
This Recommendation defines a new XHTML document type that is based upon the module framework and modules defined in Modularization of XHTML [XHTMLMOD]. The purpose of this document type is to serve as the basis for future extended XHTML 'family' document types, and to provide a consistent, forward-looking document type cleanly separated from the deprecated, legacy functionality of HTML 4 [HTML4] that was brought forward into the XHTML 1.0 [XHTML1] document types. This document type is essentially a reformulation of XHTML 1.0 Strict using XHTML Modules. This means that many facilities available in other XHTML Family document types (e.g., XHTML Frames) are not available in this document type. These other facilities are available through modules defined in Modularization of XHTML, and document authors are free to define document types based upon XHTML 1.1 that use these facilities (see [XHTMLMOD] for information on creating new document types).
W3C (2001). Design>Web Design>Standards>XHTML
#23126
The library is committed to serving the entire public, and that means striving to ensure that all pages of our site are accessible to the greatest possible number of people and devices (including audio browsers, Braille readers, and other specialized browsing environments).
New York Public Library (2004). Design>Web Design>Accessibility>XHTML
#29983
But one of the lesser known differences between HTML and XHTML is that attributes within tags (such as the href attribute within a link tag) must use 'entities' for special reserved characters. For example, within mark-up, & has a special meaning. Greater than and less than signs (> and <) also have a special meaning, as they are used to define tags.
HyperWrite (2004). Articles>Web Design>Standards>XHTML
#25736
XHTML by Example: A Hybrid Layout 
In this chapter, we’ll roll up our sleeves and apply what we’ve learned about XHTML thus far to mark up a real-world design project. The markup we create will be partly structural, partly transitional, and fully standards-compliant.
Zeldman, Jeffrey. PeachPit Press (2005). Design>Web Design>XHTML
#20462
This guide was created to help out all those who want to learn more about programming and designing scalable, modular and easy to maintain websites. HTML is hard enough! This eases the seasoned HTML programmer into fluent XHTML
Onaicul Project, The (2001). Design>Web Design>XHTML
#28347
This document is version 1.1 of XHTML Modularization, an abstract modularization of XHTML and implementations of the abstraction using XML Document Type Definitions (DTDs), and XML Schemas. This modularization provides a means for subsetting and extending XHTML, a feature needed for extending XHTML's reach onto emerging platforms. This specification is intended for use by language designers as they construct new XHTML Family Markup Languages. This specification does not define the semantics of elements and attributes, only how those elements and attributes are assembled into modules, and from those modules into markup languages. This second version of this specification includes several minor updates to provide clarifications and address errors found in the first version. It also provides an implementation using XML Schemas.
W3C (2006). Design>Web Design>Standards>XHTML
#20512
In this tutorial you will learn the difference between HTML and XHTML. You will also learn how this Web site was converted to XHTML.
#26650
XHTML Web Design for Beginners
Explores exactly what XHTML is, and how you can use it to start producing the next generation of Web pages.
Peck, Nigel. SitePoint (2003). Design>Web Design>Standards>XHTML
#27717
XHTML, HTTP accept-header and MIME-type application/xhtml+xml
In 2005 it is high time to start serving XHTML as XML on a grand scale. Others have been doing it for years. I have been doing it since Christmas. Switching between XHTML as xml and text/html is easy using the HTTP accept header.
Tverskov, Jesper. Smack the Mouse (2005). Design>Web Design>HTML>XHTML
