XHTML - Wikipedia, the free encyclopedia
Popularity Report
 |
|||
|
|||
|
|||
|
|||
|
|||
|
Rank
URL Tag Cloud
Bookmark History
Saved by 12 people (-5 private), first by anonymouse user on 2006-06-24
- Bengarrett77 on 2009-10-23 - Tags xhtml , Help
- Beconomist on 2009-06-19 - Tags Programming
- Thanhbv on 2009-04-07 - Tags no_tag
- Changheelee on 2009-02-09 - Tags html , wikipedia , xhtml
- Jeiseman on 2008-08-17 - Tags LI843 , XHTML
Public Sticky notes
Because they need to be well-formed, true XHTML documents allow for automated processing to be performed using standard XML tools
Highlighted by praphulcs
Highlighted by changheelee
XHTML
Highlighted by changheelee
XHTML
Highlighted by changheelee
The Extensible Hypertext Markup Language, or XHTML, is a markup language that has the same depth of expression as HTML, but also conforms to XML syntax
Highlighted by praphulcs
true XHTML documents allow for automated processing to be performed using standard XML tools—unlike HTML, which requires a relatively complex, lenient, and generally custom parser. XHTML can be thought of as the intersection of HTML and XML in many respects, since it is a reformulation of HTML in XML
Highlighted by praphulcs
XHTML is an application of XML, a more restrictive subset of SGML. Because they need to be well-formed, true XHTML documents allow for automated processing to be performed using standard XML tools—unlike HTML, which requires a relatively complex, lenient, and generally custom parser. XHTML can be thought of as the intersection of HTML and XML in many respects, since it is a reformulation of HTML in XML. XHTML 1.0 became a World Wide Web Consortium (W3C) Recommendation on January 26, 2000. XHTML 1.1 became a W3C Recommendation on May 31, 2001.
Highlighted by beconomist
XHTML is "a reformulation of the three HTML 4 document types as applications of XML 1.0"
Highlighted by beconomist
"The XHTML family is the next step in the evolution of the Internet. By migrating to XHTML today, content developers can enter the XML world with all of its attendant benefits, while still remaining confident in their content's backward and future compatibility."
Highlighted by beconomist
The need for a reformulated version of HTML was felt primarily because World Wide Web content now needs to be delivered to many devices (like mobile devices) apart from traditional desktop computers, where extra resources cannot be devoted to support the additional complexity of HTML syntax.[citation needed] In practice, however, HTML-supporting browsers for such constrained devices have emerged faster than XHTML support has been added to the desktop browser
Highlighted by praphulcs
Another goal for XHTML and XML was to reduce the demands on parsers and user agents in general.
Highlighted by praphulcs
With HTML, user agents increasingly took on the burden of "correcting" errant documents. Instead, XML requires user agents to give a "fatal" error when encountering malformed XML. In theory, this allows for vendors to produce leaner browsers, without the obligation to work around author errors. A side effect of this behavior is that those authoring XHTML documents and testing in conformant browsers should be more readily alerted to errors that may have gone otherwise unnoticed if the browser had attempted to render or ignore the malformed markup.
Highlighted by praphulcs
By shifting the underlying base from SGML to the simpler XML, HTML would become compatible with common XML tools;[4] servers and proxies would be able to transform content, as necessary, for constrained devices such as mobile phones.
Highlighted by beconomist
A feature XHTML inherits from its XML underpinnings is XML namespaces.[citation needed] With namespaces, authors or communities of authors can define their own XML elements, attributes and content models to mix within XHTML documents.
Highlighted by praphulcs
The changes from HTML to first-generation XHTML 1.0 are minor and are mainly to achieve conformance with XML. The most important change is the requirement that the document must be well-formed and that all elements must be explicitly closed as required in XML.
Highlighted by praphulcs
Public Comment