intertwingly

It’s just data

RSS Bandit

Dare Obasanjo: So this morning I decided to write an RSS News aggregator.

My advice is to test it on Joe's and Shelley's feeds. This requires two simple, albeit a bit unconventional, rules: anything in the namespace of the DocumentElement is equivalent to the null namespace, and items can be either inside or outside of channels.

And then there are synonyms, e.g., dc:subject vs category...


Managing Change

Morgan Delagrange: But it's moot if we abandon all rigor in our dependencies.

Agreed. [Maven | Centipede] for daily development, Gump for advanced warning.

One place I differ, however, is that I think that there is an easier solution than requiring developers to perform extra steps. All it takes is for people to take notifications of gump failures seriously and follow this advice.

Meanwhile, a big thanks for all of your help this week!


Pics: ASF Board

B. W. Fitzpatrick posted some pictures from the last ApacheCon.

Left to right: Ken Coar, Greg Stein, Roy Fielding, Jim Jagielski, Ben Laurie, Dirk Willem van Gulik, Brian Behlendorf, Sam Ruby

Auld Lang Syne

As promised, as of the end of the last year, I am no longer updating 0101679. The content remains, and the entries for the last month contain both a prominent visual indication of the new blog as well as an automatic redirect.

On the odd chance that any of the remaining orbiting space junk suddenly decides to reactivate, I'm posting the contents of my intertwingly RSS 0.91 feed over at http://radio.weblogs.com/0101679/rss.xml.

We'll tak' a cup o' kindness yet...

Good-night and joy be wi' you


RSS Best practices: description

Steven Noels and Ugo Cei are discussing XML encoding of descriptions, using one of my feeds as an example.

For starters, I do provide an RSS 0.91 feed with encoded descriptions because that's what many people have grown to expect. But I also provide an RSS 2.0 feed with some added goodies and better conformance to best practices. The descriptions have had their HTML stripped, and the full content is available as content:encoded. Aggregators like aggie do just fine with this.

I have plans to provide a separate excerpt in the future.