I've had a hard time "getting" RDF (e.g. how it differs from XML), but this article helps give it context. The semantic web is being built simultaneously from the bottom up and top down. Typifying the bottom-up approach, RDF content is machine-readable at the outset; powerful but complex (with several advantages over microformats), RDF is all about inter-operability. Top-down approaches introduce "metadata sprinkling" to existing content, simple but limiting by comparison e.g. microformats (using CSS class attributes as in hCard), or meta elements (meta tags such as those for geo-discovery). Both approaches are valid, but RDF is hard whereas microformats help "the rest of us" contribute to the semantic web. There may be a collision ahead, however, between microformats and RDFa (sprinklings of RDF embedded in existing XHTML).
Tag archive for 'xhtml'
Previously we looked at moving to jQuery, and then at the best way to do corners and gradients using a variety of techniques (Part 1). In this follow-on article (Part 2) I want to share how jQuery can be extended for similar cornering, gradient, and drop shadow visual effects. Although my JavaScript ability is not much beyond "cut and paste" the idea here is to share how easy it is to create these effects for other folk possessed by similar (in)ability.
Continue reading 'Corners, gradients and shadows with jQuery'
Rounded corners. Yes, they may be a "Web 2.0" fashion fad, but it has been clearly documented that they're a lot easier to make than square ones. As part of my overhaul of bioneural.net I've been optimizing much of the code "under the hood", meaning a lot of the changes aren't even visible. Re-evaluating how things are put together, and considering how they could be done more efficiently or otherwise improved is a valuable exercise—that it scratches a perfectionist itch is an added bonus. In this article I look at a variety of methods for creating boxes with rounded corners and gradients. Yep, it's a showdown!
Continue reading 'The best way to do corners and gradients'
As if Blue-ray v HD-DVD wasn't enough: the W3C's HTML 5 spec is now a working draft (interestingly edited by Google and Apple employees), competition to XHTML 2. HTML 5 extends HTML (yet the iframe lives on!) to cover the semantics of "non-document" web content e.g. forums, search engines, e-shops, etc. But do the differences mean developers must eventually choose one flavour or the other?
The first version of my site preference panel for WordPress needed lots of JavaScript for the toggle (Proto.aculo.us), more JavaScript to switch styles, and still more JavaScript to change text size. Version 2 still uses JavaScript for the toggle effect—but no additional load—since jQuery is already utilised by K2. The rest is accomplished using server-side PHP, and the revised 3-column panel layout makes use of more recent CSS know-how. I've tried to modularize the preferences panel as much as possible, but some simple template editing is still required (at 4 points). It is optimised for K2 (tested using RC3 and RC4) and although I haven't tested it with other themes (that's your job!) I don't see why it couldn't be used (*Some tweaking may be required. Batteries not included.)
Continue reading 'bioneural.net site preference panel revisited'
If you had viewed the source of my WordPress-generated pages a while ago you'd have noticed that my head elements were a real mess. Now they've been spring cleaned, arranged neatly into related groupings and the needless clutter disposed of. Plugins that use the wp_head hook distribute junk all over the show, offending any sense of order. Luckily your WordPress theme is the key to taking control of your head, through a combination of edits to functions.php and header.php.
Continue reading 'Spring clean your WordPress head'
