X/HTML5 and XHTML2

Comments: After learning about the progress of XHTML 2, let's take a look at the progress of X/HTML 5. X/HTML 5 cool's concept of Chapter elements X/HTML 5 introduces new elements to divide Web pages into several chapters. These components help search engines and auxiliary tools better understand the page content. Use these new elements to make tags more readable. Unit-based
After learning about the progress of XHTML 2, let's take a look at the progress of X/HTML 5.
Where is X/HTML 5 cool?
Conception of Chapter Elements
X/HTML 5 introduces new elements to divide Web pages into several chapters. These components help search engines and auxiliary tools better understand the page content. Use these new elements to make tags more readable.
The idea of chapter-based content is cool! However, let's take a look at why the topic technology is not cool.
Dialog Element
The dialog element is used to represent a conversation. It includes a dt element used to define the speaker and a dd element that represents the speaker's speech. For example:
<Dialog>
<Dt> Costello </dt>
<Dd> Look, you gotta first baseman? </Dd>
<Dt> Abbott </dt>
<Dd> Certainly. </dd>
<Dt> Costello </dt>
<Dd> Who's playing first? </Dd>
<Dt> Abbott </dt>
<Dd> That's right. </dd>
<Dt> Costello </dt>
<Dd> When you pay off the first baseman every month, who gets the money? </Dd>
<Dt> Abbott </dt>
<Dd> Every dollar of it. </dd>
</Dialog>
Figrue Element
Headers are often used in printed and published media objects (such as photos, illustrations, and charts. So far, the Web markup language has no structure that can produce this effect. The figrue element has a legend sub-element that can be used to specify the image header. For example:
XML/HTML code
<Figure>
<Legend> Credit: Media Inc., 2007 </legend>

</Figure>
M Element
The m element indicates that a piece of text is marked or highlighted. This is useful when the search keyword is displayed on a dynamic web page. In this case, the m element can be used to mark the keywords on the page. For example, in response to the keyword snow searched by a user, the following content can be generated on the Web page:
XML/HTML code
<P> A <m> snow </m> man is a man-like sculpture constructed out of <m> snow </m>. </p>
The input element is enhanced.
After the input element function is enhanced, data types such as email, url, Data, time, and number are supported. This means that more verification functions can be completed on the client.
Open Process
The development process of X/HTML is much more open than that of XHTML 2. Everyone can participate in the X/HTML 5 Creative details.
X/HTML 5 highlights
Use of Chapter Elements
The idea of using Chapter elements is good, but the application of X/HTML 5 seems a little cumbersome. Some explanations may even confuse you. For example:
The aside element represents a part of the page content. It is associated with the content before and after the aside element. It can be seen as an independent part of the content. These components are often used for side bars in printing technology.
Isn't the div element with the role attribute more extensible and understandable?
Another mentioned Chapter element is nav, which is used to indicate links to other pages on the page. Do we really need the nav element? The nl element in XHTML 2 can better complete this task.
Shortcomings in HTML 4 and XHTML 1 will exist in Future specifications.
Because X/HTML tries to provide backward support, deficiencies in HTML 4 and XHTML 1 will still exist in X/HTML 5. The specification does not need to be left blank. Instead, the client software should provide backward compatibility by supporting multiple specifications.
X/HTML 5 does not follow the X/HTML 5 manual
X/HTML 5 is designed to be backward compatible with HTML 4 and XHTML 1. At present, big, acronym, u, and tt are not in this specification, and other elements such as I and samll have a new definition. For example, in the HTML 4.01 specification, I and small are defined as follows:
I: italic text
Small: displays text in "small" font
In X/HTML 5, I and small have new meanings:
Elements I use different methods to represent a text section or a paragraph that is different from the text, such as classification design, technical terms, idioms in external languages, an idea, opinion, ship name, or other texts that need to be italic in printing technology ..
The small element presents a small print font (the part in the document that describes the legal constraints, such as copyright or existing drawbacks) and comments.
By redefining the meaning of I and small, this undermines backward compatibility with HTML 4 and XHTML 1. This is because backward compatibility should mean that the HTML 5 user agent (browser) should be consistent with the HTML 4 user agent when rendering HTML 4 documents. Therefore, if HTML 5 emphasizes backward compatibility, the structure with little significance in HTML 4 also has little significance in HTML 5.
No, right? Still supports font elements?
Yes. If the developer uses the WYSIWYG editor, X/HTML 5 still supports font elements. Is it reasonable to do so? Can WYSIWYG editor avoid using font?
WYSIWYG Signature
Documents generated using the WYSIWYG editor must contain the following WYSIWYG signature in the head element:
XML/HTML code
<Meta name = "generator" content = "(WYSIWYG editor)"/>
Or:
XML/HTML code
<Meta name = "generator" content = "Sample Editor 1.0 (WYSIWYG editor)"/>
What is the reason for doing so? A sign of shame? Does it need to tell the browser to make the worst preparations, because this document is generated using the WYSIWYG editor? So what if only one part of the document is completed using the WYSIWYG tool?
Pre-defined class names are supported.
The predefine class name is the semantic CSS class name reserved in the X/HTML 5 user proxy. In the following example, copyright is a predefined class name:
XML/HTML code
<P class = "copyright>... </p>
Other predefined classes include "error", "example", "issue", "note", "search", and "warning ". What's more troublesome is that some predefined class names are only used in some specific elements and cannot be used in other elements. For example, the class name "copyright" is only used in p and span elements. The class name "error" is only used in p, section, span, and strong.
A problem with predefine class names is that the following statements have no significance:
XML/HTML code
<P class = "important">

This method makes sense:
XML/HTML code
<P class = "copyright">
Rewriting the class attribute makes it difficult to describe the specific meaning of the structure. For example, what does the following code mean:
XML/HTML code
<P class = "important copyright issue">
The predefined class name also limits the developer's freedom to use the class name. Similarly, if a developer uses a non-predefined class name, but the class name becomes a predefined class one day later, what will happen first? Does this change the meaning of the developer's previous content?
HTML 5 v. s. XHTML 5
In an attempt to finally solve the debate between HTML and XHTML, the X/HTML 5 specification makes things more difficult to understand. Indeed, the X/HTML 5 specification does mean that "generally, developers can still directly use XML in the Web", even though W3C has been continuously working hard for the future application of XML in the Web.
The development process is too hasty
X/HTML 5 is designed to cope with W3C's delay in updating HTML 4 and XHTML 1. As a result, the development process of X/HTML 5 is a little in a hurry. I feel that this specification does not know where it suddenly came out and then quickly followed up. Even developers who are directly involved in the development process feel that the standard development process is a bit impractical.
Competition in the next generation of Markup Language
Both X/HTML 5 and XHTML 2 are competing to replace HTML 4 and XHTML 1. In the early stages of development, some browser vendors have claimed their preferences for these two specifications. Due to the urgency and closeness of the review, the Web standards organization is polarized. With the development of the two specifications, more development resources and market funds will be invested in one of them. All these factors will lead to a "standard" war.
Every one of us is the creator of this standard, because the Web belongs to everyone. Only an honest and open debate can ensure that the best standards are the winners.
Note: For ease of reading, the "HTML 4.x/ XHTML 1. x" is abbreviated as "HTML 4 and XHTML 1"
Connection: http://www.dudo.org/article.asp? Id = 249