Nor is it a distant relative of alphabet soup. (Or maybe it is...)
The next version of web markup language is moving forward in its slow-as-molasses way. The biggest thing about XHTML 2.0 is that it’s divided into modules for compartmentalisation of updates, revisions, and such.
Other highlights, at least in this version, include:
- continued support for bidirectional languages, such as Arabic and Hebrew (take that, Microsoft!)
- full frontal use of the
objecttag, eventually replacingimgandapplet(don’t cry; it’s not as apocalyptic as it sounds) - continued support of the various
metaelements, including adding aprofileattribute — so even if you think Google isn’t checking your page’s meta tags, don’t delete them, they’re still the coin of the realm - expamding the
hrefattribute to any element, not just toa...so any item, including a table, could be made into a link without having to use theatag. Just be cautious how this gets used
It isn’t live yet, it’s still in committee; so don’t change your doctype tags just yet. The browsers won’t support some of the features; and if history is anything to go on, some of them won’t even when this working draft becomes a recommendation.
And...does anyone else remember seeing the paragraph stating that at this time the W3C believes that there are no patent disclosures associated with the XHTML 2.0 specification? That worries me. I’m slowly but surely ceasing to encourage patents of web technologies by boycottimg companies that try to enforce the ridiculous (no more Amazon links as of tomorrow, for example). Does this mean that markup languages will soon be patented, either in full or in part?
Posted by Laughing Muse • 275 views • Share this link • Newer • Older
Click here to join