About HTML5_html/css_WEB-ITnose

I have been learning XHTML before, and now I am preparing to start HTML5. I have some non-technical questions. I would like to ask someone who understands to explain:
1. I have read in a book that when the W3C released the XHTML standard It is announced that HTML5 will no longer be developed in the future, but will focus on XHTML and develop in the direction of XML. So what is the status of HTML5? Has W3C abandoned its original route?
2.HTML5 is not based on SGML or XML, what’s going on? Isn’t XML the future development direction? Has the route deviated?
Please ask experts to clarify these two directional issues.

Reply to discussion (solution)

The first question you have to ask W3C

"Separation of structure and presentation" Will the thought continue forever? Does HTML5 still respect this principle?

1. What is said in the book may not be accurate
2. HTML5 is compatible with previous html and xhtml. There is no strict verification like xml at all
Just write in the header of the document

IE6 does not understand html5

1. What is said in the book may not be accurate
2. html5 is compatible with previous html and xhtml. There is no strict verification like xml at all
Just write in the document header
The key is that W3C is also developing XHTML2.0. I saw that there is information about XHTML2.0 and HTML5 on the website. There are some discussions on the competition between 0, but they are basically from 2007 and 2008. It seems that XHTML2.0 has disappeared recently. I just don’t understand the development direction of WEB standards. Is W3C declining? There is also HTML5 What are the basic concepts of ?
For example, XHTML has brought us the idea of ​​"separation of structure and presentation" and the development direction of XML. What about HTML5? Do you still stick to this idea and general direction?

IE6 does not know html5
Well, all browsers do not fully "know" html5, haha

1. What is said in the book may not be accurate
2. HTML5 is compatible with the past html and xhtml. There is no strict verification like xml at all
Just write in the document header
In addition, does html5 still follow the strict syntax required in xhtml? For example, tags must be closed, properly nested, etc. Are these the future direction?

Refer to http://blog.sina.com.cn/u/2760399482

What I understand about html5 is not html but xhtml css3 canvas and a series of collections

What I understand about html5 is not html but xhtml css3 canvas and a series of collections
html5 is not a collection of xhtml, css3, etc., it is independent

html5 adds head/foot Waiting for labels is for semantics.

Quote from the 4th floor’s reply:

ie6 doesn’t know html5

Well, all browsers don’t fully “know” html5, haha ​​
Although ie6 -ie8 does not support html5 but just adding a very simple js file can make the new elements of html5 display in earlier versions of ie.

It seems that the recent replies are a little off topic. . .

In 1998, W3C decided not to continue promoting HTML. They believed that xml was the future. Therefore, version 4.0.1 of the HTML specification was frozen, and a new specification called In the case of self-closing tags, etc., adding two kinds of content (actually three, if you focus on HTML frames) there is an XHTML transitional form to help people move to the gold standard of XHTML strict forms.

This is going great, and it encourages a generation of developers to think about efficient, well-structured code. Work then began on the xhtml 2.0 specification, which was a revolutionary change to the language as it broke backward compatibility in order to become more logical and better designed.
However, a small portion of Opera's population does not believe that XML is the future for all web developers. These individuals performed additional work to demonstrate that it was possible to extend HTML forms without violating backwards compatibility specifications. The specification eventually became web forms 2.0 and was subsequently added to html5.
In 2006, the w3c admitted that they were overly optimistic in expecting the field to move to xml.
The re-started HTML working group voted to use whatwg's web applications specification as the basis for the new version of HTML.

In 2009, W3C stopped working on xhtml2.0 and shifted resources to html. As a result, html5 clearly won this theoretical battle.

IE6 has become history, HTML5 is the future of the Web, and browsers will only become more and more advanced, so the days of leaving IE6, 7, and 8 are just around the corner

IE6 has become history, HTML5 is the future of the Web, browsers will only become more and more advanced, so the days of leaving IE6, 7, and 8 are just around the corner
Currently, the world is dominated by HTML5, this is Fact, but isn’t XML the future of WEB? Is the transition from XHTML to XML a bad route? I feel that XML is relatively powerful in storing and exchanging information~

w3c is a unified web standard, and it will definitely continue after the separation of structure and style! xhtml1.0 is the standard of html! In the future, standard browsers can parse standard codes!

w3c is a unified web standard, and the separation of structure and style will definitely continue! xhtml1.0 is the standard of html! In the future, standard browsers can parse standard codes!
Now W3C also has an XHTML working group, which is working on the standardization of XHTML2.0. This was originally W3C’s plan for the future route (that is, HTML??XHTML??XML), but who would have expected that HTML5 would come out halfway? And with the support of major browsers, it had to be adopted as a standard by W3C and became the mainstream today. This affected the W3C route to a certain extent and directly led to the tragic situation that no one cares about XHTML2.0 and does not know the WEB standard. Will the future direction of HTML5 change?

This is going great, and it encourages a generation of developers to think about efficient, well-structured code. Work then began on the xhtml 2.0 specification, which was a revolutionary change to the language as it broke backward compatibility in order to become more logical and better designed.
However, a small portion of Opera's population does not believe that XML is the future for all web developers. These individuals performed additional work to demonstrate that it was possible to extend HTML forms without violating backwards compatibility specifications. The specification eventually became web forms 2.0, and was later added to htm...
Thank you very much. I have been looking for historical details about the dispute between html5 and xhtml2.0, and finally found it ~

For its first five years (1990-1995), HTML went through a number of revisions and experienced a number of extensions, primarily hosted first at CERN, and then at the IETF.

With the creation of the W3C, HTML's development changed venue again. A first abortive attempt at extending HTML in 1995 known as HTML 3.0 then made way to a more pragmatic approach known as HTML 3.2, which was completed in 1997. HTML4 quickly followed later that same year.

The following year, the W3C membership decided to stop evolving HTML and instead begin work on an XML-based equivalent, called XHTML. This effort started with a reformulation of HTML4 in XML, known as XHTML 1.0, which added no new features except the new serialization, and which was completed in 2000. After XHTML 1.0, the W3C's focus turned to making it easier for other working groups to extend XHTML, under the banner of XHTML Modularization. In parallel with this, the W3C also worked on a new language that was not compatible with the earlier HTML and XHTML languages, calling it XHTML2.

Around the time that HTML's evolution was stopped in 1998, parts of the API for HTML developed by browser vendors were specified and published under the name DOM Level 1 (in 1998) and DOM Level 2 Core and DOM Level 2 HTML (starting in 2000 and culminating in 2003). These efforts then petered out, with some DOM Level 3 specifications published in 2004 but the working group being closed before all the Level 3 drafts were completed.

In 2003, the publication of XForms, a technology which was positioned as the next generation of Web forms, sparked a renewed interest in evolving HTML itself, rather than finding replacements for it. This interest was borne from the realization that XML's deployment as a Web technology was limited to entirely new technologies (like RSS and later Atom), rather than as a replacement for existing deployed technologies (like HTML).

A proof of concept to show that it was possible to extend HTML4's forms to provide many of the features that XForms 1.0 introduced, without requiring browsers to implement rendering engines that were incompatible with existing HTML Web pages, was the first result of this renewed interest. At this early stage, while the draft was already publicly available, and input was already being solicited from all sources, the specification was only under Opera Software's copyright.

The idea that HTML's evolution should be reopened was tested at a W3C workshop in 2004, where some of the principles that underlie the HTML5 work (described below), as well as the aforementioned early draft proposal covering just forms-related features, were presented to the W3C jointly by Mozilla and Opera. The proposal was rejected on the grounds that the proposal conflicted with the previously chosen direction for the Web's evolution; the W3C staff and membership voted to continue developing XML-based replacements instead.

Shortly thereafter, Apple, Mozilla, and Opera jointly announced their intent to continue working on the effort under the umbrella of a new venue called the WHATWG. A public mailing list was created, and the draft was moved to the WHATWG site. The copyright was subsequently amended to be jointly owned by all three vendors, and to allow reuse of the specification.

The WHATWG was based on several core principles, in particular that technologies need to be backwards compatible, that specifications and implementations need to match even if this means changing the specification rather than the implementations, and that specifications need to be detailed enough that implementations can achieve complete interoperability without reverse-engineering each other.

The latter requirement in particular required that the scope of the HTML5 specification include what had previously been specified in three separate documents: HTML4, XHTML1, and DOM2 HTML. It also meant including significantly more detail than had previously been considered the norm.

In 2006, the W3C indicated an interest to participate in the development of HTML5 after all, and in 2007 formed a working group chartered to work with the WHATWG on the development of the HTML5 specification. Apple, Mozilla, and Opera allowed the W3C to publish the specification under the W3C copyright, while keeping a version with the less restrictive license on the WHATWG site.

Since then, both groups have been working together.

The HTML specification published by the WHATWG is not identical to this specification. At the time of this publication, the main differences were that the WHATWG version included features not included in this W3C version: some features have been omitted, but may be considered for future revisions of HTML beyond HTML5; and other features were omitted because at the W3C they are published as separate specifications.

A separate document has been published by the W3C HTML working group to document the differences between the HTML specified in this document and the language described in the HTML4 specification. [HTMLDIFF]
我也找到了一些，摘自W3C网站上HTML5最新working draft中关于history的叙述（http://www.w3.org/TR/html5/introduction.html#history-1），有需要的看一看吧，谢谢楼上朋友们的回复~