Lines Matching full:documents

100 trademark</a>, <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document
119 of its publication. Other documents may supersede this document. The
147 updated, replaced or obsoleted by other documents at any time. It is
158 <p>A list of current W3C Recommendations and other technical documents
257 <li>XHTML documents are XML conforming. As such, they are readily viewed,
259 <li>XHTML documents can be written to
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
294 exchange of scientific and other technical documents, suitable
297 semantic tags suitable for authoring relatively simple documents.
307 led to compatibility problems for documents across different
385 Conforming XHTML Documents, depending upon the context. The term
391 be used by Conforming Documents nor to be supported by a
398 requirement. With respect to documents, the word "should" is to
399 be interpreted as recommended programming practice for documents
400 and a requirement for Strictly Conforming XHTML Documents.</dd>
485 that retrieves and processes XHTML documents. See <a href="#uaconf">User Agent Conformance</a> for …
490 documents</span> are verified against the associated <span class="term">DTD</span>, ensuring that t…
512 conforming XHTML documents, which are restricted to tags and
515 expressed in <abbr title="Resource Description Format">RDF</abbr> within XHTML documents.</p>
518 Documents</a></h3>
586 not required in all XML documents. XHTML document authors are strongly encouraged to use XML declar…
595 documents are not strictly conforming XHTML 1.0 documents as
597 conformance for documents involving multiple namespaces.</p>
653 to be a validating user agent, it must also validate documents
766 <h2><a name="h-4.1" id="h-4.1">4.1 Documents must be
795 <p>XHTML documents must use lower case for all HTML element and
918 documents.</p>
949 ensure that XHTML 1.0 documents are well-structured XML documents, XHTML 1.0
950 documents MUST use the <code>id</code> attribute when defining fragment
955 compatible when serving XHTML documents as media type <code>text/html</code>.
964 <p>Although there is no requirement for XHTML 1.0 documents to be
966 accomplish. Guidelines for creating compatible documents can be
974 <p>However, XHTML Documents which follow the guidelines set forth
979 XHTML documents.</p>
1032 of documents. Conformance to a document profile provides a basis
1034 the facilities required to process documents of that type, e.g.
1042 different versions of documents for different clients.</p>
1142 wish their XHTML documents to render on existing HTML user
1174 documents backward compatible is likely to not work as expected in XML-based
1210 converting existing HTML documents. The values of these attributes
1252 <li>Applications that access XHTML documents served as Internet media type
1257 <li>Applications that access XHTML documents served as Internet media types
1292 will reduce this effect for documents which are served without
1317 CSS defines different conformance rules for HTML and XML documents;
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>
1440 in XML documents by associating them with namespaces identified