I’m back from my holiday, with a quick look at some of the links I would have discussed in more detail had I been here…
The W3C have announced that they have relaunched activity on HTML:
After the publication of HTML 4… W3C set forth to turn HTML into an XML-based format, called XHTML, due to the benefits of XML formats. The first full XHTML Recommendation was issued in early 2000. But due to the significant legacy of Web content that is some variant of HTML, traditional browser vendors moved slowly to adopt XHTML. This, in turn, has meant little motivation for content developers to adopt XHTML for the traditional desktop environment. Leaders in the Web developer and design communities therefore urged W3C to renew its commitment to HTML…
W3C is pleased to relaunch work on HTML with strong support from its Members and more staff resources (including people and hardware). W3C has tailored the HTML Working Group Charter to enable active participation from browser vendors, applications designers, and content developers, whose joint participation is key to the success of the future HTML.
Over at the Wired blog they’re pondering on the best way to provide licensing information on images; the author suggests a new attribute for img, something like lic="license-abbr". I think the main problem with this is that it doesn’t provide any information about what that license is, or its terms.
The Microformats solution is rel-license; basically, putting a link to the license description in the rel attribute of a link, as so:
<a href="http://creativecommons.org/licenses/by/2.0/" rel="license">cc by 2.0</a>
John’s Essential Guide to CSS is a ‘pocket guide’ to the language. There are many out there, but I decided to link to this one because of it’s very first link: Fix Your Site with the Right DOCTYPE.
I cannot stress enough the importance of working to a valid DOCTYPE; it’s good for the web, and it’s good for web developers. I remember the Eureka! moment of discovering how DOCTYPEs work, when all of a sudden cross-browser coding became that much easier. It’s an absolute basic of web development, so if you’re not familiar with how it works then I suggest you read the article forthwith.
I made my first forays into web development back in 1998, with my own Geocities homepage (now sadly defunct). It was after I developed my first ‘proper’ website (an unoffical guide to the FIFA Club World Championship 2000; please don’t laugh, this was eight years ago…) that I decided I wanted to be a professional developer.
I’m mostly self-taught, but there’s no way I would have been able to make a career out of it – and keep interested in it – without the aid of the books below.
Please note: I’m not saying that these are necessarily the best books available, just that they have been – and continue to be – inspirational to me. OK, in no particular order…
The next milestone build of my favourite browser, Firefox, has been released today. Codenamed Gran Paradiso, the biggest changes have been made to the graphics layer, which is now Cairo. I’ve played around with it a little today, and it seems significantly faster at painting a page than its predecessor.
I took a look at the Mozilla Developer Centre page to see a fuller list of new features, and noticed that it now supports the CSS :default pseudo-class. This was a surprise to me, as I’d never heard of it! The information in the W3C recommendation document is very vague: