Lines Matching full:xhtml
1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "dtds/xhtml1-strict.dtd">
3 <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
5 <title>XHTML 1.0: The Extensible HyperText Markup
62 <h1 class="head"><a name="title" id="title">XHTML</a><sup>™</sup> 1.0:
122 Language">XHTML</abbr> 1.0, a reformulation of HTML
128 extensibility of XHTML. Compatibility with existing HTML user
197 <li class="tocline">1. <a href="#xhtml">What is XHTML?</a>
204 <li class="tocline">1.3 <a href="#why">Why the need for XHTML?</a></li>
217 <li class="tocline">3. <a href="#normative">Normative Definition of XHTML 1.0</a>
263 <h1><a name="xhtml" id="xhtml">1. What is XHTML?</a></h1>
265 <p>XHTML is a family of current and future document types and modules that
266 reproduce, subset, and extend HTML 4.0 <a href="#ref-html4">[HTML]</a>. XHTML family document types are <abbr title="Extensible Markup Language">XML</abbr> based,
272 <p>XHTML 1.0 (this specification) is the first document type in the XHTML
278 their content to XHTML 1.0 will realize the following benefits:</p>
281 <li>XHTML documents are XML conforming. As such, they are readily viewed,
283 <li>XHTML documents can be written to
285 HTML 4.0-conforming user agents as well as in new, XHTML 1.0 conforming user
287 <li>XHTML documents can utilize applications (e.g. scripts and applets) that rely
290 <li>As the XHTML family evolves, documents conforming to XHTML 1.0 will be more
291 likely to interoperate within and among various XHTML environments.</li>
294 <p>The XHTML family is the next step in the evolution of the Internet. By
295 migrating to XHTML today, content developers can enter the XML world with all
357 <h2><a name="why" id="why">1.3 Why the need for XHTML?</a></h2>
359 <p>The benefits of migrating to XHTML 1.0 are described above. Some of the
360 benefits of migrating to XHTML in general are:</p>
366 attributes. The XHTML family is designed to accommodate these extensions
367 through XHTML modules and techniques for developing new XHTML-conforming
368 modules (described in the forthcoming XHTML Modularization specification).
376 platforms. The XHTML family is designed with general user agent
380 develop XHTML-conforming content that is usable by any XHTML-conforming
415 Conforming XHTML Documents, depending upon the context. The term
430 and a requirement for Strictly Conforming XHTML Documents.</dd>
445 facility, is not a Strictly Conforming XHTML Document.</dd>
516 that retrieves and processes XHTML documents. See <a href=
541 XHTML 1.0</a></h1>
546 <p>This version of XHTML provides a definition of strictly
547 conforming XHTML documents, which are restricted to tags and
548 attributes from the XHTML namespace. See <a href=
549 "#well-formed">Section 3.1.2</a> for information on using XHTML
551 expressed in <abbr title="Resource Description Format">RDF</abbr> within XHTML documents.</p>
556 <p>A Strictly Conforming XHTML Document is a document that
573 <p>The root element of the document must designate the XHTML
575 "#ref-xmlns">[XMLNAMES]</a>. The namespace for XHTML is
577 <code>http://www.w3.org/1999/xhtml</code>.</p>
590 PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
594 PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
598 PUBLIC "-//W3C//DTD XHTML 1.0 Frameset//EN"
604 <p>Here is an example of a minimal XHTML document.</p>
610 PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
612 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
624 not required in all XML documents. XHTML document authors are strongly encouraged to use XML declarations in all their documents. Such a declaration is required
628 <h3><a name="well-formed" id="well-formed">3.1.2 Using XHTML with
631 <p>The XHTML namespace may be used with other XML namespaces
633 documents are not strictly conforming XHTML 1.0 documents as
637 <p>The following example shows the way in which XHTML 1.0 could
642 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
661 <p>The following example shows the way in which XHTML 1.0 markup
674 <p xmlns='http://www.w3.org/1999/xhtml'>
691 an XHTML document for well-formedness. If the user agent claims
701 <li>When a user agent processes an XHTML document as generic XML,
703 <code>ID</code> (e.g. the <code>id</code> attribute on most XHTML elements)
739 single line-feed character, that is passed up to the application. The XHTML
803 <p>Due to the fact that XHTML is an XML application, certain
836 <p>XHTML documents must use lower case for all HTML element and
846 This omission is not permitted in XML-based XHTML. All elements
934 <p>In XHTML, the script and style elements are declared as having
991 Therefore, in XHTML 1.0 the <code>id</code>
993 ensure that XHTML 1.0 documents are well-structured XML documents, XHTML 1.0
999 compatible when serving XHTML documents as media type <code>text/html</code>.
1001 <p>Note that in XHTML 1.0, the <code>name</code> attribute of these
1003 subsequent version of XHTML.</p>
1008 <p>Although there is no requirement for XHTML 1.0 documents to be
1018 <p>However, XHTML Documents which follow the guidelines set forth
1023 XHTML documents.</p>
1028 <p>XHTML 1.0 provides the basis for a family of document types
1029 that will extend and subset XHTML, in order to support a wide
1032 mechanism will enable the extension and sub-setting of XHTML 1.0
1037 <p>As the use of XHTML moves from the traditional desktop user
1038 agents to other platforms, it is clear that not all of the XHTML
1040 held device or a cell-phone may only support a subset of XHTML
1043 <p>The process of modularization breaks XHTML up into a series of
1056 <p>It provides a formal mechanism for sub-setting XHTML.</p>
1060 <p>It provides a formal mechanism for extending XHTML.</p>
1114 XHTML-1.0-Strict</a></p>
1119 XHTML-1.0-Transitional</a></p>
1124 XHTML-1.0-Frameset</a></p>
1130 <p>The XHTML entity sets are the same as for HTML 4.0, but have
1138 <p><a href="DTD/xhtml-lat1.ent">Latin-1 characters</a></p>
1142 <p><a href="DTD/xhtml-special.ent">Special characters</a></p>
1146 <p><a href="DTD/xhtml-symbol.ent">Symbols</a></p>
1187 wish their XHTML documents to render on existing HTML user
1257 XHTML 1.0 DTDs. Because of this change, care must be taken when
1263 <p>Finally, note that XHTML 1.0 has deprecated the
1266 removed from XHTML in subsequent versions.</p>
1289 <h2>C.11 Document Object Model and XHTML</h2>
1296 XHTML 1.0, elements and attributes are specified in lower-case. This apparent difference can be
1300 <li>Applications that access XHTML documents served as Internet media type
1305 <li>Applications that access XHTML documents served as Internet media types
1308 Also, some XHTML elements may or may
1316 extraneous elements, XHTML has made the elements optional.
1334 <h2>C.13 Cascading Style Sheets (CSS) and XHTML</h2>
1345 CSS style sheets for XHTML should use lower case element and
1354 <li>Within the XHTML name space, user agents are expected to
1360 <li>Within the XHTML name space, user agents are expected to
1366 be aware that the HTML rules apply to XHTML documents delivered as
1367 HTML and the XML rules apply to XHTML documents delivered as XML.</li>
