|

providing graphic design, branding, photography and marketing expertise to denver and the world
|
Quote
of the Week:
All solitary dreamers know that they hear differently when they close their eyes. -Gaston Bachelard
|
|
Notes from Notchcode
7.23.2009
XHTML 2 dumped, HTML 5 ascendant. Does it matter?
Here's the short version: XHTML was based on XML, back in the '90s when people thought XML was the future.
As mentioned in Techworld.com a while back:
XHTML 2 will not become a W3C standard, [W3C spokesperson Ian] Jacobs said. "We're investing in HTML 5 for the future," he said. Work stops on the XHTML language, but W3C still plans an XML formulation of HTML 5, to be done by the HTML working group.
A prominent AJAX and web development proponent applauded the W3C decision.
Firefox and Safari also include HTML 5 support, as well as Google's Chrome and Android.
So, what's the practical difference for us web designers and developers; people who need to know the code underneath the user experience, but aren't necessarily considered "coders"?
XHTML info from Mike:
XHTML 2.0 is based solely on XML, forgoing the SGML heritage and syntax peculiarities present in current web markup. XHTML 2.0 is supposed to be a “general-purpose language,” with a minimal default feature set that is easy to extend using CSS and other technologies (XForms, XML Events, etc). It’s a modular approach that allows the XHTML2 group to focus on generic document markup, while others develop mechanisms for presentation, interactivity, document construction, etc.
...and HTML 5:
While XHTML 2.0 aims to be revolutionary, the HTML working group has taken a more pragmatic approach and designed HTML 5 as an evolutionary technology. That is to say, HTML 5 is an incremental step forward that remains mostly compatible with the current HTML 4/XHTML 1 standards. However, HTML 5 offers a host of changes and extensions to HTML 4/XHTML 1 that address many of the faults in these earlier specifications.
Read his post for more.
Another post explaining the difference had a nice example of the structural, easy-to-understand nature of XML:
<farm>
<barn>
<horses>10</horses>
<tools>
<hammers>1</hammer>
<shovel>2</shovel>
</tools>
</barn>
<field>
<cows>8</cows>
<pigs>30</cows>
</field>
</farm>
The structure shows the hierarchy of elements, and makes no effort to style of make them act a certain way. XHTML is simply a version of HTML that is valid XML code.
HTML 5 will contain more support for web applications, APIs, and other stuff that wasn't as built-into earlier versions of HTML. And as mentioned above, it will be (mostly) backward-compatible with BOTH HTML and XHTML.
So why, or should, we care? Probably not a lot, at the moment. But be prepared to make adjustments in the nearish future, and bone up on the new specification with the Definitive Guide of your choice. O'Reilly, here I come, once again!Labels: advice, coding, W3C, web design, XHTML
posted at 9:51 AM
Leave your comments here:
0 comments
Leave your comments here:
0 comments


|