Back in the old days (maybe in Web 0.9) Analog, the popular web analysis program, automatically added a ‘Valid HTML’ button at the bottom of each report page it produced. This was before the W3 Consortium took up the banner of validation, so the button was provided by a third-party site (webtechs.com). Either through a ‘clerical error’ or an invoice not paid the domain name being used to supply the image lapsed - and it was then taken over by someone else who decided to add in a completely inappropriate picture with the same filename.

If we move forward to the present day, then in Web 2.0 the idea of bringing in content from other sources is the distinct flavour of the month. In some cases this is still just images (for badges), but the norm is either to have RSS feeds (essentially bringing in HTML code, usually with no filtering …

As I was coming to terms with the harsh reality of being awake at the end of last week, I caught an appeal on behalf of the Disasters Emergency Committee (DEC) on the radio. It set me to thinking again (with the aid of coffee) how they could benefit from building a badge/widget response network.

The typical patterns for badges/widgets are either to provide ongoing functionality (e.g. Flickr badges or Google Adsense) or to offer something time-limited for a specific campaign. For someone like the DEC where the timescales are compressed the second option isn’t really worth pursuing. They do have a Rapid Response Network for more traditional media outlets, e.g the main television and radio networks, the national newspapers, etc.

I think they could benefit enormously from providing a badge/widget that is available all the time. If there’s an appeal happening then content connected with that is delivered, otherwise …