Overview

Modularization is also intended to help content creators. As more and more devices become web-enabled, the number of platforms a content creator will be asked to support will become unreasonable. By dividing HTML up into different ‘building blocks’ content creators can supply a minimal version of their site for user agents that only support the Basic module, a moderate version of their site for user agents who support the additional modules, and a full version of their site for user agents that support the full range of the XHTML specification.

Finally the X in XHTML was intended to help people who wish to extend HTML. The use of XML brought a standard grammar with which they could define their extension, and the modularization meant that their extension would be just another module that a user agent developer or content creator could choose to support. Additionally, since XHTML pages should state what modules are required to accurately render them, the user agent software could dynamically load a ‘plug-in’ that it could use to render a module that was defined after the user agent had been originally released.

For more information, go to:

HTML 4.0—http://www.w3.org/TR/1999/REC-html401-19991224

XHTML™ 1.0—http://www.w3.org/TR/2002/REC-xhtml1-20020801

XHTML™ Basic—http://www.w3.org/TR/2000/REC-xhtml-basic-20001219/

XHTML™ 1.1—http://www.w3.org/TR/2001/REC-xhtml11-20010531/

XHTML Tables Module - XHTML™2.0—http://www.w3.org/TR/2004/WD-xhtml2-20040722/mod-tables.html

For the purposes of this guide, it is assumed that you have experience in HTML and XHTML programming or access to someone who has such experience.

How to Create Applications

You can design the following types of applications:

Web browser

Company directory

Stock ticker

1 - 3

Page 9
Image 9
Polycom SIP 2.2.0 manual How to Create Applications