A user tries to follow the Echos of the RSS debate

Echo: Stop the madness!.

Log Format Roadmap. There seems to be quite some excitement around Ram Ruby’s Roadmap. At first I was a little skeptical on the project (why not calling it YASF as in Yet Another Syndication Format?). After reading Tim Bray’s why we need a new format at all I think that it’s worth a try. Recent history tells us that the main divide was between people saying “It has to be powerful and thus not necessarily easy to understand, we will build tools to manage the complexity” and others saying “It has to be simple so that anybody will be able to hack new solutions using it without being an expert”. Both positions make sense. You don’t really need to understand how the jpeg format works to create cool images, but at the same time all of us learned html looking at other people’s pages, because it was relatively easy to understand. Ultimately it’s only a matter of a very little number of tools vendors, most of them small companies, agreeing on a new standard and changing the world. [Paolo Valdemarin: Paolo’s Weblog]

My first thoughts were “don’t we have enough format arguments as it is?”  I guess I am less skeptical now.  Maybe this is a chance to end the madness and get our collective shit together.

I like the sound of Echo as a name for the new format (much more than PIE).  I think a new name is essential to avoid getting into squabbles about RSS 1.5, 3.0, whatever…

I would prefer that it not use RDF unless that is absolutely necessary.  If there are advantages to having RDF available then Danny Ayers has already shown how this can be achieved.  On the other hand I would like to see some advantage taken of the work that has been done on topic maps, like XTM, XFML and ENT.

I’m also hopeful that Dave’s comment (I was a little suprised not to find a permalink) indicates that he will support the new format although I notice he has not added his name to the list of supporters.

[Curiouser and curiouser!]

Matt pulls together a good collection of posts on what’s been going on in trying to specify a format for weblog posts. The place I found the most usefuf starting point was Tim Bray’s explanation of why we need a new format at all. I found it nicely user oriented.

I depend on other people’s efforts to build the tools I use to do my work. When the engineering debates spill over into incompatibilties and inconsisentcies among the tools my life is harder. As one current example, I would like to subscribe to the RSS feed from the blog thought?horizon. I used to subscribe but it got upgraded to something that my current aggregator tool chokes on. I could send David Buchan an email and point out the problem. Or not.

As a user I don’t really care about the pissing contests that developers like to play. I don’t have the time or the patience to deal with them. I’ve been an early adopter of technology since before I knew what that was. I’m willing to tinker and I like to understand how things work. But I don’t like getting whipsawed. If Bill Gates and Microsoft do something annoying it’s usually time to BOGU. When it’s one of the little guys I’ll place one or two bets and then I get annoyed and then I go somewhere else. 

I want to find ways to support and encourage the innovations like weblogs and wikis that get built because some smart programmer has an itch they need to scratch. I think I get an edge from finding tools before the rest of the pack. And I like to help bring those tools to others who trust me. One way that I control my risk is to make sure that I can get my data in and out of formats that I have some reason to believe are reasonably standard and wide spread. Right now I mostly watch these arguments, worry a lot, and hope they’ll get resolved so I can get on with managing my information environment.

A present from Lilia in my aggregator

  Sweeping in front of your doors

David Buchan points to the quote by Jim McGee that I missed with my vacation:

There’s an old story that I’ve heard described as a Russion proverb. It says that if each one of us takes care of sweeping the sidewalk in front of our own home, we won’t need streetsweepers. It’s worth thinking about how that might apply to the world of knowledge work, both on the level of being an individual knowledge worker yourself and on the level of helping make the other knowledge workers that surround you more effective.

1. Great metaphor to use thinking about knowledge workers.

2. I was curious about Russian proverb as I can’t easily recall it (although it looked familiar). I did a search and found that this is a citation from Leo Tolstoy that is used in slightly different variants as a proverb (or may be he used the proverb in his writing?).

In original it looks like (my not perfect translation from Russian version):

Don’t ask others to do things you can do yourself. Let everyone sweep in front of his or her door. If each [of us] will do it, the whole street will be clean.

[Mathemagenic]

Here’s a wonderful illustration of what makes blogging so much fun and why aggregators are the only way to keep up with the flow. Lilia’s Mathemagenic is one of the blogs that have been in my subscription lists for months. She’s been away, but picks up on one of my posts from two weeks ago. She tracks down the story behind something I’ve used and enriches it for me in a way that I could never find on my own. And it all shows up in my aggregator for when I’m ready to look at it. I don’t have to remember to go check her site. I don’t risk missing the post because it scrolls off the front page into the archives. And, in its own right, Lilia’s post is a nice little self-referential example of the point that I was making originally.

With RSS and my aggregator working for me, these wonderful little gifts show up on a regular basis.

A welcome present from Unbound Spiral

RSS Feed Full Posts.

A couple of reminders recently to provide readers with what they really want.  RSS Feeds that contain the full post.  It’s now done – isn’t choice wonderful?  You can choose.  If you desire a full post rather than the excerpt, please change your subscription to:

Full Posts (XML) http://www.henshall.com/blog/index2.rdf 

Why is it that MT’s default setting is excerpts?

Makes me think about my own newreader.  I wish I could toggle between full and excerpts.  Even better scan quickly on excepts and then toggle to full posts.  Early on I tried AmphetaDesk and currently just use the Radio one.  Except I get posts that blow its formating from time to time.  Is there a newreader that can improve my experience?  Is there one I can install on my server? That is also easy to do?How does a group go collective newsreading?  A my, yours, ours subscription file? Are there tools mapping subscriptions in this format? 

[Unbound Spiral]

Of course, I updated my subscription list right away. I’ve been tracking Stuart’s excellent observations on the world of knowledge work for a while now. With full feeds it will be that much easier.

Stuart does raise some important points about some needed evolution in RSS feed readers. One tool that I have added to the mix that helps in my “Radio” environment is Mikel Maron’s MyRadio tool. It lets me do some of the things Stuart asks for.

RSS from the user’s side

really simple shit. I love “RSS”. I love my aggregator. I want the two to work in harmony for a long, long time. If I understand correctly, several blogtool vendors are making up their own versions of rss as they go along. Most of these new formats won’t work with my aggregator unless adaptations are made. This doesn’t make any sense to me, if you want your blogtools to become popular, wouldn’t you want the established base be able to read them? Reminds me of railway history, where newcomers developed incompatible ‘broad-gauge‘ trains and tracks. Go ahead and learn from this history, the outcome is as predictable. [Adam Curry: Adam Curry’s Weblog]

Like Adam, I consider myself a technology user, albeit one that is willing to pop the hood and poke at things myself rather than wait for the mechanic to arrive.  I too love RSS and my aggregator. They are the ‘secret sauce’ that gives me immense control over my information environment.

For example, I just checked, and I am currently subscribed to 236 news sources in “Radio”‘s aggregator. I rarely surf to these sites and don’t particularly care what stories look like in context. I get annoyed with sites that don’t provide a full RSS feed and insist on offering snippets or headlines only. Sites that provide no RSS feed essentially don’t exist for me. Selfish? Certainly. Shortsighted and apt to miss something of importance to me? Possibly, although I expect I’ll hear about it from one of my sources that does provide an RSS feed.

95% of my online information comes to me by way of my aggregator. For much of what I am interested in — business uses of information technology and knowledge management related topics — important stories hit my aggregator two to three weeks before they show up in conventional online sources.

I have been following the recent debates over variations in RSS formats in a bemused sort of way. Engineers are always convinced that they can do a better job than the next person. Have you ever browsed the parts bins in a hardware store? I suppose that when engineers were debating the merits of philips head, flat head, and torx screws it certainly mattered to them who did what when. I just want things to more or less work together.

I’m enough of a weekend tinkerer and early adopter that I will tolerate a certain amount of breakage from time to time. If I don’t have the right screwdriver I’m likely to just pound on things with a bigger hammer. But I do get annoyed when people try to invent new screws to sell their brand of screwdriver instead of trying to solve a real problem of connecting things.

One of the risks of choosing to be an early adopter is that I’ll end up picking tools that fail to pass the test of time. In that sense, standards do matter to me as protection against bad choices. The data that makes up what I’ve posted here since October of 2001 is in a format that protects me from the worst of those risks. And that does matter.

Scoble draws faulty analogies between Starbucks and Microsoft

Alex Hoffman writes his own answer to Eric Kidd: “he needs to change his focus away from technology, platforms and the development community, to real world end-users and their requirements.”

One last thought. My family just went out to dinner. On the way back we passed by our favorite coffee place. Named Victor’s. Hey, wait a minute. This is Redmond. Not far from Starbucks’ headquarters. In Eric’s world, Victor would never be allowed to sell coffee.

Every day Victor reminds me that someone can beat “the dominant corporation” and deliver a better product.

Think that Victor doesn’t have a chance? 25 years ago you probably were the one saying “no fast-food franchise has a chance against McDonalds.” But, look at the per-store sales of In-N-Out vs. McDonalds and you’ll see that In-N-Out is another example of a dominant player getting their lunch eaten.

[The Scobleizer Weblog]

The fundamental problem with this analogy and the several others that Scoble offers is that none of these other industries are subject to the network effects that software platforms are. Scoble’s argument is that other big, dominant, competitors proved vulnerable to competition so Microsoft is vulnerable too.

What he conveniently overlooks is the critical differences in the markets we are talking about. In software platforms, unlike markets for expensive coffee, it matters what other customers are doing. Imagine, if you will, a coffee market that was similar to the operating systems market. In that market, if I bought coffee at Victor’s I wouldn’t be able to have a conversation with anyone who bought coffee at Starbucks without permission from Starbucks. Or imagine a world where you had to get permission from the zoning board and Starbucks to open a coffee shop. Then you’re getting closer to the world that platform vendors like Microsoft get to play in.

So, Scoble, here’s a question for you. When you’re evangelizing Longhorn in days to come, will you be just talking about some whizbang new feature or might you mention in passing the eleventy gazillion users in the installed base?

Learning from others mistakes – this is broken

This Is Broken: Bad Design from Good Experience.. Ever notice design errors in everyday things? Send them in for a post-mortem to mark at goodexperience dot com. He’s cataloging them at This Is Broken. Learning from mistakes. [a klog apart]

One of the powers of imagination is that we have the opportunity to learn not just from our own mistakes, but also from the mistakes of others.  Repeating others’ mistakes is a singular waste of time. You don’t make progress unless you’re making new and interesting kinds of mistakes.

I’m reminded of a comment I first came across reading the proceedings of the 1968 NATO conference on software engineering (one of those classics in the field which I unfortunately gave away years ago, glad to see it is available on the web). Paraphrasing Newton’s remark that he had seen farther by standing on the shoulders of giants, software engineering had mostly been characterized by “standing on each others’ feet”.   

Must ‘clueful politician’ be an oxymoron?

Lots of commentary and reactions to Orrin Hatch’s recent less than clueful remarks. Laughter and ridicule seem to be the most appropriate response so I appreciated this effort from Terry Frazier. Twitting the other recent nonsense about someone trying to lay claim to the term clue-by-four seems like a nice bonus.

I’m surprised that Hatch didn’t also endorse the “No Mental Theft Act“

Hatch to Endorse Snipers for Cubs ‘Rooftop Viewers’. AP News (www.aggravatedpress.com) is reporting this morning that Sen. Orrin “Hatchetman” Hatch, R-Utah, spoke at a DC-area Lions Club dinner Wednesday evening on the critical problem of copyright theft.

[…] Referring to the lawsuit filed by the Chicago Cubs baseball team to stop local building owners from watching games without paying a fee Hatch said “I’m all for peaceful settlements in cases like this, but there is no excuse for breaking copyright laws. These people have been warned. If the Cubs want to hire some snipers and pick these thieves off the rooftops I’m all for it. And they shouldn’t be held liable. A few dozen sniper shootings and people will think twice about watching baseball games without a ticket.” Hatch — best known as a deeply religious folk music artist, a technophobe, and a fan of long underwear — also serves in the US Senate when he’s not out advocating corporate attacks on private American citizens. […] Hatch, whose patriotic folk hit, America United includes the line “Those who would divide us could not realize, that from the smoke and ashes America would rise…United…United” received a standing ovation from the Lions Club crowd. “Copyright terrorists are evil-doers, striking at the heart of this country. They have no idea how far we’ll go to stand against them. These baseball thieves are just the beginning. Soon we’ll be destroying computers, cleaning up the Internet, and saving our children and future generations by any means necessary!” As the crowd filed out of the crumbling auditorium to the parking lot they were met by throngs of teenagers — all waiting to drive their aging grandparents home. Dozens of cliques had formed around users with Apple iPods and they were eagerly trading their favorite re-mixes and singles, as the beats of pirated tunes boomed from car stereo speakers. “Look at these fine young Americans,” said a clueless Hatch. “All waiting here to help their elders. These are the young people we care about, the ones we need to protect from the evil-doers. Yes sir. These young people are the future of our country.” […] [AP News]

Author’s note: The above story is satire. In keeping with the spirit and antics of our political leaders it is puerile, mean-spirited, even borderline moronic. But I feel better. Copyright laws in this country are no joke. Artists and creators deserve protection, but the paying public has rights as well. Congress has forgotten this and has allowed a tiny handful of mega-corporations to lock away our culture and our heritage. We deserve better. Now go out and convince the good people of Utah to hit Senator Hatch with an electoral clue-by-four™. [b.cognosco]

Mapping our way to knowledge management

Part of successful knowledge management in organizations will revolve around how good a job we do at drawing “maps” that help explain and represent this new territory. Dane Carlson offers pointers to some resources we can adapt to that task.

You Are Here: Maps 101. How to create a good map. I’ll remember this for the next Talk Like a Pirate Day. via The Map Room: A weblog about maps, a good read itself…. [Dane Carlson’s Weblog]

In the wonderful serendipity that using a news aggregator offers, Frank Patrick’s Focused Performance weblog (a great resource on project management brings the following tidbit:

A Clarification on Maps and Plans. A Clarification on Maps and Plans — I recently quoted Alford Korzybski, using his often cited statement,

“A map is not the territory.”

Upon researching it, I didn’t go far enough. The complete statement from is actually…

“A map is not the territory it represents, but if correct, it has a similar structure to the territory, which accounts for its usefulness.”

Puts a whole ‘nother spin on it, doesn’t it?

Project plans and schedules can be made to model a “similar structure” to the project itself, sufficiently reflecting reasonable expectations of the future as well as uncertainty to be useful. (I think someone — who was it? — once said that “all models are wrong, but some models are useful.” If that’s so, then I’m comfortable with the idea that some models are more useful than others.) [Frank Patrick’s Focused Performance Blog]

If those of us talking about knowledge management are exploring new territory, one of our responsibilities is to draw the maps that will encourage those who stayed behind to follow us and show them paths that are safe and interesting to travel.

Blogging for knowledge workers–think compound interest and start tomorrow

Why PhDs should start blogging.

Things New PhDs Should Start Doing [via José Luis Orihuela]

  1. Keep a Research Diary
  2. Maintain an Electronic Bibliography
  3. Know Your Search Engines
  4. An Archiving System for Useful Info
  5. Learn The Composition of your Research Community
  6. Document Useful Learning Experiences
  7. Keep a Professional Home Page
  8. Maintain an Updated CV
  9. Get Involved Early On
  10. Develop Research Meta-awareness

This article provide a good reference to justify why PhDs should start blogging 🙂

[Mathemagenic]

This is a much richer post than its title might suggest. What it really offers is a nicely thought out and articulated mini-case about what any aspiring knowledge worker ought to be doing to get more leverage out of their work.

While it’s never too late to start these kinds of strategies for yourself, the earlier you do, the sooner you’ll start building and refining your own private, custom-designed and organized knowledge base. Youe specifics may vary, but this provides a good road map to what you ought to be thinking about. And if you can’t generalize and abstract from the world of a Ph.D. student to your own world of knowledge work, then perhaps you ought to start looking for one of those nice 1950s assembly line jobs that don’t exist anymore.

It’s just like compound interest, the sooner you start the better.

If the only tool you have is a hammer…

A Day In My Life, By Bill Gates. (SOURCE:Scobleizer Radio Weblog)-PREDICTION: Within 10 years, the centre of most knowledge workers (including Bill Gates) will be a blog type application. NOT email. <quote> I’d say that of my time sitting in my office, that is, time outside of meetings, which is a couple of hours, two-thirds of that is sitting in E-mail. E-mail is really my primary application, because that’s where I’m getting notifications of new things, that’s where I’m stirring up trouble by sending mail out to lots of different groups. So it’s a fundamental application. And I think that’s probably true for most knowledge workers, that the E-mail is the one they sit in the most. Inside those E-mails they get spreadsheets, they get Word documents, they get PowerPoints, so they navigate out to those things, but the center is E-mail. </quote> [Roland Tanglao’s Weblog]

Roland catches the real point of this interview with Gates. The interview provides some interesting raw data on the day-to-day work practices of our economy’s quintessential knowledge worker. Email is the tool he has for communications so it is the tool that he uses. It is worth seeing how Gates thinks through how to get leverage from the tools that he has available. We all need to exercise that kind of thought about how to use our knowledge tools — blogs and aggregators included.