为什么 HTML5 和 XHTML 2 是不同的标准？
这两个标准分开制定有什么原因吗？ 他们似乎在解决同样的问题，但有什么区别？如果他们要保持独立，他们预计在未来的网络开发中扮演什么角色？
Is there a reason why these two standards are being developed separately? They seem to be solving the same problem but what are the differences and, if they are to remain separate, what roles are they expected to take in web development in the future?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（5）
浏览器供应商非常关心向后兼容性。 制定 XHTML2 的小组却没有这么做。
请注意，XHTML2 并没有解决 HTML5 正在解决的所有相同问题。 HTML5 的范围比 XHTML2 广泛得多。 HTML5 涵盖了处理模型、JavaScript API、视频、音频、应用程序小部件等，但 XHTML2 没有。
至于预期角色，顶级浏览器供应商的代表会参与 HTML 工作组，但不参与 XHTML2 工作组。 另一方面，对“Backplane”感兴趣的人们正在参与XHTML2 WG。
另请参阅David Baron 关于 W3C 工作原理的帖子。
Browser vendors care a great deal about backwards compatibility. The group speccing XHTML2 didn’t.
Note that XHTML2 isn’t solving all the same problems HTML5 is solving. HTML5 is much broader in scope than XHTML2. HTML5 covers processing models, JavaScript APIs, video, audio, application widgets, etc. but XHTML2 does not.
As for expected roles, representatives from top browser vendors participate in the HTML WG but not in the XHTML2 WG. On the other hand, people showing interest in the “Backplane” are participating in the XHTML2 WG.
See also David Baron’s post about how the W3C works.
这篇文章只回答了部分问题。 它没有解释这两个标准将来可能扮演的角色。：
X/HTML 5 与 XHTML 2
至于可能的角色，人们说：
如果浏览器供应商不这样做支持XHTML 2的话我不知道它的作用是什么。 另一方面，XHTML 2 或多或少可以转换为 XHTML 1，例如使用 XSL 转换，因此在我看来，如果任何人愿意的话，它比 HTML 5 更容易支持将。
This article only answers part of the question. It doesn't explain what the likely roles of the two standards will be in the future.:
X/HTML 5 Versus XHTML 2
As for the likely roles, people are saying that:
If browser vendors don't support XHTML 2 then I don't know what its role is. On the other hand XHTML 2 can be more-or-less converted to XHTML 1, e.g. using an XSL transformation, so it seems to me that it would be (much) easier for anyone to support, if they wanted to, than HTML 5 will be.
XHTML2 已死。
看看面向网页设计师的 HTML5 的第一章杰里米·基思（Jeremy Keith）以总结的方式出色地解释了这些差异。
XHTML2 is dead.
Have a look at the first chapter of HTML5 FOR WEB DESIGNERS by Jeremy Keith which explains superbly the differences in a summarized way.
IMO，这在很大程度上是一个准确的解释，但应该注意的是，HTML5 不向后兼容 - 即使在 IE7 中也无法使用 CSS 来设置新元素（例如section）的样式。 是的，有 JavaScript 解决方法，但这些还不够，因为不是每个人都启用了 JavaScript，也不是每个开发人员都会意识到这些，同样也不是每个开发人员都有能力以这种方式使用 JavaScript。
This is largely an accurate explanation, IMO, but it should be noted that HTML5 isn't backwards compatible - new elements like section cannot be styled with CSS in even IE7. Yes, there are JavaScript work-arounds but these aren't sufficient, both because not everyone has JavaScript enabled, far from every developer will become aware of these, and similarly not every developer has the ability to use JavaScript in this way.
HTML 5 的构建考虑了向后兼容性，这与 XHTML 2 不同，XHTML 2 的创建是为了摆脱向后兼容性的限制。
W3C 允许 XHTML 2 工作组到期，基本上结束了开发XHTML 2. HTML 5 具有向后兼容性和新功能，将成为未来的文档类型。
HTML 5 has been constructed with backwards compatibility in mind, unlike XHTML 2, which was created in order to break away from restrictions involved with backwards compatibility.
The W3C allowed the XHTML 2 working group to expire, essentially ending development of XHTML 2. HTML 5, with backwards compatibility and new features, will become the doctype of the future.