The colors of this site are rendered correct in MS IE 4.0+, Opera 3.6x+ and Netscape 6.0+/ corresponding Mozilla browsers. This site works overall best with the newest Opera and Mozilla browsers (details). Also Netscape 6.1+, MS IE 5.5+ for Windows, MS IE 5.0 for Mac and new NeoPlanet browsers render this site quite well. The presentation is poor with Netscape 4.x and it has some clear rendering errors. It doesn't render either advisory titles of some elements and all internal links don't work.

I list below all topic groups, which I have done according to subjects, which they handle. You can return to this topic group by using this menu and the link Table of topic groups on the top of the each page.
6. XHTML 1.1 modules
Attribute Collections This is acceptable.

Nothing to report.

HTML, HEAD, TITLE, BODY Structure Module

These are core elements of the XHTML Basic™, which is the "mother" of all XHTML-family based languages.


These are basic text elements of the XHTML Basic™, which is the "mother" of all XHTML-family based languages.

This module doesn't have directly presentational elements (for example B) but structural and phrasal elements. Blooberry alias Brian Wilson classify presentational elements as Physical styles and phrasal elements as Virtual styles. Physical Styles have direct affect to the presentation, but Virtual Styles don't have exactly defined physical effects, but they preserve the semantic meaning of the elements. W3C might have thought at the same way, when it classified SUB and SUP among Inline Presentational elements.

Because the sub-classification Inline Phrasal doesn't have SUB and SUP elements the the XHTML™ Basic doesn't have elements to express footnotes, simple mathematic formulas and some units (for example mm3). If SUB and SUP don't clear contain some semantic meaning also to non-visual browsers. We must ask, what could describe footnotes and units, which use superscript in non-visual browsers. If they don't have any kind of Virtual Styles, the information must be delivered through some phrasal elements with semantic classes (for example <var class="superscript">) or annotations.

In principle it is acceptable, that SPAN is called as a structural element, because it doesn't do anything by itself.

W3C: XHTML Basic™; Modularization XHTML™: Inline Phrasal, Structure Module, Text Module.
Blooberry: Character Formatting.
A Hypertext Module

It is a basic element of the XHTML Basic™, which is the "mother" of all XHTML-family based languages. Only the element A belongs to this module. The element A can have several attributes, which belong different modules.

Other notes: A.
W3C: XHTML Basic™; Modularization XHTML™: Hypertext Module, Text Module.
DL, DT, DD, OL, UL, LI List Module

These are basic elements of the XHTML Basic™, which is the "mother" of all XHTML-family based languages.

It is consistent, that DIR and MENU are not in this module.

W3C: XHTML Basic™; Modularization XHTML™: List Module, Text Module.
APPLET Applet Module
OBJECT Object Module

OBJECT belongs to the XHTML Basic™, which is the "mother" of all XHTML-family based languages.

Presumably APPLET doesn't belong to the basic DTD of XHTML 1.1 but is an additional module in XHTL-family languages.

W3C: XHTML Basic™; Modularization XHTML™: Applet Module, Object Module.
HR + B, BIG, I, SMALL, SUB, SUP, TT Presentation Module

In principle this module is unnecessary, but it is quite ok. The element HR is the only block level element in this module. Normally block-level elements are not used as presentational elements but instead structural and semantic (phrasal) elements. In my mind this is however partially correct, because HR has no content and it is commonly used as presentational purposes. It can be understood also structural to divide the content of the page to logical sections.

W3C: Modularization XHTML™: Presentation Module.
DEL, INS Edit Module

Browsers don't support the actual functionality of these elements.

W3C: Modularization XHTML™: Edit Module.
Bi-directional Text Module This module is ok.

Nothing to report.

W3C: Modularization XHTML™: Bi-directional Text Module.
Basic Forms Module, Forms Module These modules are ok.

Nothing to report.

W3C: Modularization XHTML™: Basic Forms Module, Forms Module.
Basic Tables Module, Tables Module These modules are acceptable.

But could the attribute cols added to the element TABLE, because WML 1.2 use it and if WML is in future a part of XHTML family, WML could need it. This attribute could increate the download speed, because the browser doesn't need to check how many columns the table has. I could have partially the same effect as table-layout:fixed, which I handle in my CSS-site.

Other pages: Tables ([S]).
W3C: Modularization XHTML™: Basic Tables Module, Tables Module.
Image Module, Server-side Image Map Module These modules are acceptable.

These modules use the IMG element. Basic attributes to IMG are the same as in the XHTML 1.0 Strict document type except that usemap belongs to Server-side Image Map Module.

W3C: Modularization XHTML™: Image Module, Server-side Image Map Module.
Client-side Image Map Module This module is acceptable.

In addition to elements MAP and AREA, attributes coords and shape to A and usemap to OBJECT belong also to this module.

W3C: Modularization XHTML™: Client-side Image Map Module.
Frames Module This module is ok.

This is used with the Target Module.

Other notes:Target Module.
W3C: Modularization XHTML™: Frames Module.
Target Module This module is ok.

This is commonly used with the Frames Module.

Other notes: Frames Module.
W3C: Modularization XHTML™: Target Module.
Iframe Module This module is ok.

Read however notes to the usage of the attribute name from Name Identification Module.

Other notes: Name Identification Module.
W3C: Modularization XHTML™: Iframe Module.
Intrinsic Events Module This module is ok.

Nothing to report.

W3C: Modularization XHTML™: Intrinsic Events Module.
Base Module, Metainformation Module, Scripting Module, Link Module These modules are ok.

Nothing to report.

Stylesheet Module, Style Attribute Module These modules are acceptable.

The style attribute destroys the purpose of style sheets and it is not recommended to use. That's why it is an own module. But in some exceptional cases it might be reasonable to use it in handwritten documents.

W3C: Modularization XHTML™: Stylesheet Module, Style Attribute Module.
Name Identification Module This module is deprecated.

In XHTML 1.1 the attribute name is in general deprecated in the use of name identification (= to work as a fragment identifier or an unique identifier of an element) to elements A, APPLET, FORM, IFRAME, FRAME, IMG, MAP and OBJECT. Because the Name Identification Module is deprecated, it is then highly non-recommended to use. If XHTML is delivered as XML, user agents, which follow strictly XML principles are not obliged to read the attribute name as the fragment identifier of the element. User agent might break this rule. That's why I have listed it in this table and in HTML 4.01/ XHTML 1.0 and XHTML 1.1 tables at the same background color as proprietary attributes. At least authors should define also id with the same value.

Other notes: Legacy Module.
W3C: Modularization XHTML™: Name Identification Module.
Legacy Module This module is acceptable.

Because one the main aims of HTML 4.0 was to separate content and presentation from each others and replace FONT and other pure presentational elements and attributes with CSS, this module is used in exceptional cases, where users have much old browsers.

Other notes: BASEFONT.
W3C: Modularization XHTML™: Legacy Module.
Ruby Annotation Module This module is ok.

This is an internationalization module like the Bi-directional Text Module.

Copyrights Tapio Markula 1999-2001 (@dnainternet.net) - not into the public use without the permission (add to beginning of the e-mailaddress my name, Tapio Markula, separated with a comma).
Information about browsers, which render or print this site best.
Help pages has been last edited 09.09.2003

[Get Opera!] [Get Mozilla!]