Polycom VR-6000 ユーザーズマニュアル

 Overview

1 - 3

where XHTML was divided up into ‘modules’, where any features above and 

beyond a skeleton set were grouped into individual modules. User agent (UA) 

developers could then decide which extensions to support. A simple user 

agent can be considered a fully compliant user agent by supporting only the 

Basic module, whereas a more powerful browser can support all the official 

modules, as well as those developed by third parties.
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:

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. 

You can design the following types of applications:

• Web browser