7.2. XHTML Modularization (XHTML Basic and 1.1)
Modularization of XHTML came on the heels of the XHTML 1.0 specification. With the HTML details wrapped inside the XML (extensible) mechanism, it wasn't a very big conceptual leap to break up the large set of elements into logical groups of modules (although it took some time to hammer out the details). The XHTML modularization activity occurred somewhat independently of how the modules would potentially be packaged in future recommendations.
One set of modules were bundled together under the recommendation called XHTML Basic. In many ways, XHTML Basic is a proof of concept for the modularization activity. One of the goals of XHTML Basic was to assemble a group of modules whose elements and attributes could provide contexts for simple XHTML content—the kind of content that might be viewed in limited-display devices, such as Internet-enabled home appliances. Missing from this set, for example, is the style element, as well as all event attributes of other elements.
A more substantial group of modules found their way into the XHTML 1.1 recommendation. This recommendation represents a break from elements and practices deprecated in HTML 4 and XHTML 1.0. It does, however, provide for flexible style sheets and scripts that open up the content to dynamic content.
To give you a quick overview of the modularization of XHTML from both the global perspective and from the views of the XHTML Basic and XHTML 1.1 implementations, Table 7-1 lists the complete set of modules and indications of which modules are in each of the XHTML implementations.
Table 7-1. XHTML modularization
The XHTML 1.1 set of modules continues in the tradition of the XHTML 1.0 Strict DTD in that it excludes any elements or attributes that are even remotely tied to presentation or display characteristics. Thus, references to frames and targets that could lead to other windows do not have a place in XHTML 1.1 content markup. But, of course, the mainstream browsers have no problem with such constructs if you wish to deliver them in your pages. Moreover, scripts will continue to work their magic on DOM element object properties whose corresponding attributes may be missing from the DTDs. For example, an XHTML 1.1 source document could pass validation without an iframe element explicitly mentioned in the content. But a script could dynamically create and insert such an element into the document once it has reached the client.
Copyright © 2003 O'Reilly & Associates. All rights reserved.