Wednesday, April 3, 2002

XSLT explorations (BYTE) from [IBM DeveloperWorks: XML News]. Wow! This is a typical Jon Udell article, rich with code and interesting ways of linking disparate applications. 9:30:40 AM     The Roots of Knowledge Management "We are now somewhere into the third or fourth generation of serious efforts to better manage the relationship between knowledge and organizational performance, depending on how you choose to count. I've put together a table summarizing these eras of knowledge management as a separate story. Before that time, there were a series of seminal events that constitute the roots of today's knowledge management. Since context is such an important aspect of effective KM, it's worth spending some time looking back to these roots. 1945 - Vannevar Bush - As We May Think 1967 - Doug Engelbart - Augmenting Human Intellect: A Conceptual Framework 1973 - Ted Nelson - Hypertext/Xanadu 1976 - Alan Kay - Personal Dynamic Media 1987 - Ray Ozzie - Lotus Notes 1990 - Tim Berners-Lee - WWW 1999 - Shawn Fanning - Napster/P2P Granted, a bit of an idiosyncratic list. But it does provide some useful starting points." [McGee's Musings] I wish I could take Jim's KM course. [The Shifted Librarian] 9:25:00 AM     Why Radio Kicks Ass Why Masukomi kicks ass. She describes exactly the kind of software company I want to be part of. Luckily, I am. [Scripting News] 9:06:53 AM     Soft security, Wiki, blogging, IO. Dan Green, aka DotNetDan, passes along a really thoughtful page from the MeatballWiki on tenets of SoftSecurity. It begins: AuditTrail. An audit trail tells you who did what, when. It doesn't necessarily allow you to undo what they did. It does let you know who was responsible. ReversibleChange. If anything that can be done, can be undone, no damage need be permanent. Version control is one way of making changes reversible. You can reverse a change without knowing who made it originally. DelayAction. When you can't reverse a change, delay that action until PeerReview has a chance to prevent disaster. EnforceResponsibility. Knowing who was responsible is not enough. There must be consequences. PeerReview. Your peers can ensure that you don't damage the system. Dan also wonders how Wikis and blogging/IO compare. I'd say the most basic difference is that Wikiites inhabit shared spaces, while bloggers and IOers occupy individual spaces which they then agree to federate in various ways. But it's a continuum, not an either/or distinction. Wikis also federate, and blogs and IOs can become shared spaces. Many modes to explore, many ways to learn and share. [Jon's Radio] 9:04:12 AM     Software for the People CIO:Q&A with Bonnie Nardi. The reason they often fail is that you need to have informal communications in order to find the knowledge in an organization, but the automated systems that capture such knowledge tend to be very top-down. Even passwords drive me crazy. [Tomalak's Realm] You tend to see this even in IT services organizations like ours. People ask me questions directly and I have my own group of folks that I turn to with problems. When I want to communicate solutions I gravitate towards applications that I control. If I need to get permission from central management I won't use it. 8:57:53 AM

© Copyright 2003 Peter Loats. Last update: 2/28/03; 7:16:28 PM.