Lines Matching full:xhtml
2 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "dtds/xhtml1-strict.dtd">
4 <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
6 <title>XHTML 1.0: The Extensible HyperText Markup
61 <h1 class="head"><a name="title" id="title">XHTML</a><sup>™</sup> 1.0:
108 <p>This specification defines <abbr title="Extensible Hypertext Markup Language">XHTML</abbr> 1.0, a reformulation of HTML
113 extensibility of XHTML. Compatibility with existing HTML user
173 <li class="tocline">1. <a href="#xhtml">What is XHTML?</a>
180 <li class="tocline">1.3 <a href="#why">Why the need for XHTML?</a></li>
193 <li class="tocline">3. <a href="#normative">Normative Definition of XHTML 1.0</a>
239 <h1><a name="xhtml" id="xhtml">1. What is XHTML?</a></h1>
241 <p>XHTML is a family of current and future document types and modules that
242 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,
248 <p>XHTML 1.0 (this specification) is the first document type in the XHTML
254 their content to XHTML 1.0 will realize the following benefits:</p>
257 <li>XHTML documents are XML conforming. As such, they are readily viewed,
259 <li>XHTML documents can be written to
261 HTML 4.0-conforming user agents as well as in new, XHTML 1.0 conforming user
263 <li>XHTML documents can utilize applications (e.g. scripts and applets) that rely
265 <li>As the XHTML family evolves, documents conforming to XHTML 1.0 will be more
266 likely to interoperate within and among various XHTML environments.</li>
269 <p>The XHTML family is the next step in the evolution of the Internet. By
270 migrating to XHTML today, content developers can enter the XML world with all
329 <h2><a name="why" id="why">1.3 Why the need for XHTML?</a></h2>
331 <p>The benefits of migrating to XHTML 1.0 are described above. Some of the
332 benefits of migrating to XHTML in general are:</p>
338 attributes. The XHTML family is designed to accommodate these extensions
339 through XHTML modules and techniques for developing new XHTML-conforming
340 modules (described in the forthcoming XHTML Modularization specification).
348 platforms. The XHTML family is designed with general user agent
352 develop XHTML-conforming content that is usable by any XHTML-conforming
385 Conforming XHTML Documents, depending upon the context. The term
400 and a requirement for Strictly Conforming XHTML Documents.</dd>
415 facility, is not a Strictly Conforming XHTML Document.</dd>
485 that retrieves and processes XHTML documents. See <a href="#uaconf">User Agent Conformance</a> for more information.</dd>
506 XHTML 1.0</a></h1>
511 <p>This version of XHTML provides a definition of strictly
512 conforming XHTML documents, which are restricted to tags and
513 attributes from the XHTML namespace. See <a href="#well-formed">Section 3.1.2</a> for information on using XHTML
515 expressed in <abbr title="Resource Description Format">RDF</abbr> within XHTML documents.</p>
520 <p>A Strictly Conforming XHTML Document is a document that
536 <p>The root element of the document must designate the XHTML
537 namespace using the <code>xmlns</code> attribute <a href="#ref-xmlns">[XMLNAMES]</a>. The namespace for XHTML is
539 <code>http://www.w3.org/1999/xhtml</code>.</p>
552 PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
556 PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
560 PUBLIC "-//W3C//DTD XHTML 1.0 Frameset//EN"
566 <p>Here is an example of a minimal XHTML document.</p>
572 PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
574 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
586 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
590 <h3><a name="well-formed" id="well-formed">3.1.2 Using XHTML with
593 <p>The XHTML namespace may be used with other XML namespaces
595 documents are not strictly conforming XHTML 1.0 documents as
599 <p>The following example shows the way in which XHTML 1.0 could
604 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
623 <p>The following example shows the way in which XHTML 1.0 markup
636 <p xmlns='http://www.w3.org/1999/xhtml'>
652 an XHTML document for well-formedness. If the user agent claims
662 <li>When a user agent processes an XHTML document as generic XML,
664 <code>ID</code> (e.g. the <code>id</code> attribute on most XHTML elements)
700 single line-feed character, that is passed up to the application. The XHTML
763 <p>Due to the fact that XHTML is an XML application, certain
795 <p>XHTML documents must use lower case for all HTML element and
805 This omission is not permitted in XML-based XHTML. All elements
892 <p>In XHTML, the script and style elements are declared as having
947 Therefore, in XHTML 1.0 the <code>id</code>
949 ensure that XHTML 1.0 documents are well-structured XML documents, XHTML 1.0
955 compatible when serving XHTML documents as media type <code>text/html</code>.
957 <p>Note that in XHTML 1.0, the <code>name</code> attribute of these
959 subsequent version of XHTML.</p>
964 <p>Although there is no requirement for XHTML 1.0 documents to be
974 <p>However, XHTML Documents which follow the guidelines set forth
979 XHTML documents.</p>
984 <p>XHTML 1.0 provides the basis for a family of document types
985 that will extend and subset XHTML, in order to support a wide
988 mechanism will enable the extension and sub-setting of XHTML 1.0
993 <p>As the use of XHTML moves from the traditional desktop user
994 agents to other platforms, it is clear that not all of the XHTML
996 held device or a cell-phone may only support a subset of XHTML
999 <p>The process of modularization breaks XHTML up into a series of
1012 <p>It provides a formal mechanism for sub-setting XHTML.</p>
1016 <p>It provides a formal mechanism for extending XHTML.</p>
1069 XHTML-1.0-Strict</a></p>
1074 XHTML-1.0-Transitional</a></p>
1079 XHTML-1.0-Frameset</a></p>
1085 <p>The XHTML entity sets are the same as for HTML 4.0, but have
1093 <p><a href="DTD/xhtml-lat1.ent">Latin-1 characters</a></p>
1097 <p><a href="DTD/xhtml-special.ent">Special characters</a></p>
1101 <p><a href="DTD/xhtml-symbol.ent">Symbols</a></p>
1142 wish their XHTML documents to render on existing HTML user
1209 XHTML 1.0 DTDs. Because of this change, care must be taken when
1215 <p>Finally, note that XHTML 1.0 has deprecated the
1218 removed from XHTML in subsequent versions.</p>
1241 <h2>C.11 Document Object Model and XHTML</h2>
1248 XHTML 1.0, elements and attributes are specified in lower-case. This apparent difference can be
1252 <li>Applications that access XHTML documents served as Internet media type
1257 <li>Applications that access XHTML documents served as Internet media types
1260 Also, some XHTML elements may or may
1268 extraneous elements, XHTML has made the elements optional.
1286 <h2>C.13 Cascading Style Sheets (CSS) and XHTML</h2>
1297 CSS style sheets for XHTML should use lower case element and
1306 <li>Within the XHTML name space, user agents are expected to
1312 <li>Within the XHTML name space, user agents are expected to
1318 be aware that the HTML rules apply to XHTML documents delivered as
1319 HTML and the XML rules apply to XHTML documents delivered as XML.</li>
