Lines Matching full:documents

112 "http://www.w3.org/Consortium/Legal/copyright-documents">document
134 of its publication. Other documents may supersede this document. The
163 updated, replaced or obsoleted by other documents at any time. It is
176 <p>A list of current W3C Recommendations and other technical documents
281 <li>XHTML documents are XML conforming. As such, they are readily viewed,
283 <li>XHTML documents can be written to
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
321 exchange of scientific and other technical documents, suitable
324 semantic tags suitable for authoring relatively simple documents.
334 led to compatibility problems for documents across different
415 Conforming XHTML Documents, depending upon the context. The term
421 be used by Conforming Documents nor to be supported by a
428 requirement. With respect to documents, the word "should" is to
429 be interpreted as recommended programming practice for documents
430 and a requirement for Strictly Conforming XHTML Documents.</dd>
516 that retrieves and processes XHTML documents. See <a href=
522 documents</span> are verified against the associated <span class= 
547 conforming XHTML documents, which are restricted to tags and
551 expressed in <abbr title="Resource Description Format">RDF</abbr> within XHTML documents.</p>
554 Documents</a></h3>
624 not required in all XML documents. XHTML document authors are strongly encouraged to use XML declar…
633 documents are not strictly conforming XHTML 1.0 documents as
635 conformance for documents involving multiple namespaces.</p>
692 to be a validating user agent, it must also validate documents
807 <h2><a name="h-4.1" id="h-4.1">4.1 Documents must be
836 <p>XHTML documents must use lower case for all HTML element and
962 documents.</p>
993 ensure that XHTML 1.0 documents are well-structured XML documents, XHTML 1.0
994 documents MUST use the <code>id</code> attribute when defining fragment
999 compatible when serving XHTML documents as media type <code>text/html</code>.
1008 <p>Although there is no requirement for XHTML 1.0 documents to be
1010 accomplish. Guidelines for creating compatible documents can be
1018 <p>However, XHTML Documents which follow the guidelines set forth
1023 XHTML documents.</p>
1076 of documents. Conformance to a document profile provides a basis
1078 the facilities required to process documents of that type, e.g.
1086 different versions of documents for different clients.</p>
1187 wish their XHTML documents to render on existing HTML user
1221 documents backward compatible is likely to not work as expected in XML-based
1258 converting existing HTML documents. The values of these attributes
1300 <li>Applications that access XHTML documents served as Internet media type
1305 <li>Applications that access XHTML documents served as Internet media types
1340 will reduce this effect for documents which are served without
1365 CSS defines different conformance rules for HTML and XML documents;
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>
1488 in XML documents by associating them with namespaces identified