XHTML 2.0 New Features Preview
|
<br />Before browsers can handle the next generation of XHTML, benefit from this richer content structure The XHTML 2 specification is not yet complete, but it already has many advantages over XHTML 1, including richer structural features, which make XHTML 2 an editing format that will serve as the central model for single-resource publishing systems better than its predecessor. People doing publishing, large or small, can start using the new features of XHTML 2 now, without having to wait for browsers to provide support for its new user interface features. About a year ago, an industry standards group asked me to present how XHTML2 might be useful to publishers. I had no idea if it would be practical, but they were offering to pay for a trip to New York, so I decided to investigate. The research I did didn't require much effort. XHTML 2 adds richer structure to XHTML, making it a format that can be used to create and store content, rather than just delivering content to browsers. When I say XHTML 2 is already useful, I'm exaggerating a bit; many shops have some very sensible policies regarding this unfinished standard, and XHTML 2 is still in the Working Draft stage (see Resources for more information). Unlike nearly all HTML-related standards, XHTML 2 is able to offer a lot of value before major browsers support it because it makes it possible to store content in richer and more complex structures without straying too far from familiar HTML elements and attributes. The state of XHTML: where are we now The W3C XHTML 1.0 standard creates an XML version of HTML. When browsers weren't too particular about whether a Web page was well-formed XML, Web site designers, tired of using one method for Firefox and another for Microsoft™ Internet Explorer, saw more value in standards. Many open source CSS collections (such as Open Web Design and Open Source Web Design; see Resources for links to both) use XHTML 1 sample files in their style sheets for demonstration purposes, and I've heard Web designers who barely know what well-formedness is proud to claim that their sites are written in XHTML. As Internet Explorer and Firefox supported more and more CSS features, these Web designers added more design techniques to CSS style sheets, leaving the simpler and more direct (and more easily reusable) XHTML for the basic documents. XHTML 1.1 (see Resources) did not add new features, but instead divided XHTML into modules. Its value is reflected in two aspects. First, if we find that some modules have value but others have little value, it may be easier to adopt a subset of them. For example, the Wireless Application Forum (WAP) had every reason to incorporate basic XHTML structure into its standards for delivering content to mobile phones, but it did not want to allow WAP documents to incorporate user interface features such as image maps or editing widgets that would not be very useful on a cell phone's small screen. Another benefit of a modular architecture for DTDs or schemas is that it makes it easier to plug in new modules that are specific to your application. Combined with the ability to pick and choose existing modules, this capability benefits the publishing industry: the PRISM standards group working on publishing industry metadata chose a subset of XHTML 1.1 and then added some new modules with industry-specific vocabulary to make it easier to track content through the publishing workflow. (See Resources for more information on PRISM.) You can think of developing XHTML 1.1 as cleaning out your basement: You probably won't have to throw out much stuff, you can make more use of what you already have by organizing it better, and you may even have room to set up a workbench and build something new on it. XHTML 1.1 has been a standard (or, in W3C parlance, a recommendation) since May 2001. The latest development on XHTML 2.0 is a new Working Draft published in July 2006. Although it will have to go through several stages before its final form, using the RELAX NG schema (see Resources for a link) enables us to create and use XHTML 2 documents today so that we can quickly move to XHTML when the specification becomes a recommendation. A simple XSLT stylesheet will convert these files to XHTML 1 for browser display, or you can use the CSS stylesheets available with the XHTML 2 Working Draft (see Resources) to display these documents in a browser (Firefox should work better at this point). XHTML 2: What's new? XHTML 2 retains the features of XHTML 1 that cleaned up the existing syntax to make it more concise, while also adding some new features. It adds support for XForms, the more sophisticated successor to forms that have been available in HTML for more than a decade. XHTML 2 also includes XML Events, which allow us to identify events triggered by certain user interface operations, thereby reducing the need to write scripts using JavaScript or ASP. These features will be interesting, especially once major browsers support them, but other features will be more interesting to publishers even before browsers support XHTML: A richer, more reusable structure More device independence, greater accessibility, and more semantics Easier to add metadata Previous Page 1 2 3 Next Page Read More |
<<: VMware installation of CentOS virtual machine and configuration network graphic tutorial
>>: How to configure MySQL8 in Nacos
Recommend
Vue implements the method of displaying percentage of echart pie chart legend
This article mainly introduces the pie chart data...
How to embed flash video format (flv, swf) files in html files
Flash file formats: .FLV and .SWF There are two ex...
N ways to vertically center a div with single/multi-line text (unknown height/fixed height)
When talking about this issue, some people may ask...
Vue implements a shopping cart that can change the shopping quantity
This article shares with you how to use Vue to ch...
Docker sets up port mapping, but cannot access the solution
#docker ps check, all ports are mapped CONTAINER ...
Introduction to new features of ECMAscript
Table of contents 1. Default values for functio...
Linux Jenkins configuration salve node implementation process diagram
Preface: Jenkins' Master-Slave distributed ar...
How to solve the problem of zabbix monitoring causing Chinese garbled characters in the graphical interface due to PHP problems
Solve the problem of Chinese garbled characters i...
Detailed explanation of Linux command file overwrite and file append
1. The difference between the command > and &g...
MySQL 5.7.23 decompression version installation tutorial with pictures and text
Download the MySQL installer Official download ad...
About vue component switching, dynamic components, component caching
Table of contents 1. Component switching method M...
Pure CSS to achieve the list pull-down effect in the page
You may often see the following effect: That’s ri...
5 VueUse libraries that can speed up development (summary)
Table of contents What utilities does VueUse have...
Detailed explanation of common commands for network configuration of containers in Docker
Basic network configuration Although Docker can &...
Remote development with VSCode and SSH
0. Why do we need remote development? When develo...