Jon Udell

For the next 8 or so days I will be at an undisclosed location. The following items will be absent from the scene:

• ice
• snow
• the internet

The following items will be present:

• sun
• sea
• books
• music
• rum

I’ve written a lot about MIT’s Project SIMILE since I visited the team back in December. In this week’s Interviews with Innovators I talk with Stefano Mazzocchi, the creator of Apache Cocoon, about his work on the SIMILE project. Early in the interview I asked whether he thought he was more well-known for Cocoon than for SIMILE, and he said:

Different crowds know me for different activities. And rarely do these people talk together. Well, it’s happening more now, but when I started I was one of the few people who could talk to the open source, industrial, XML-ish crowd, and to the academic, RDF, AI-ish crowd. I was kind of in the middle, and both sides didn’t really understand what I was doing with the other crowd.

I can relate to that! I seem to spend a lot of time between different worlds, trying to connect them.

It was a pleasure to finally meet Stefano for the first time in person last month, after years of correspondence and cross-blog chatter, and then also to record this interview about an approach to the semantic web that feels to me like light at the end of the tunnel.

Investigating the location of the WUMB transmitter, Doc Searls notes that while the Live Maps bird’s eye view is awesome, it’s way too hard to find and share.

Finding: For example, if I plug 42° 15′ 27″N, 71° 01′ 44″W into maps.google.com, I go straight to a real x/y place on a map. Live Maps doesn’t know what to do with it.

That appears to be true. If you know the coordinates of a location, you can find it in Google Maps using any of these formats in the search box:

42.257500, -71.028889
42° 15′ 27″N, 71° 01′ 44″W
+42° 15' 27.00", -71° 1' 44.00"

The Live Maps search box doesn’t like any of these. You could search for Hatherly Road, Quincy MA, and find it that way, but the locator page where Doc probably found the coordinates for the transmitter doesn’t know about that address.

True, most people will search for addresses, not coordinates, but I agree with Doc here, there’s no reason not to also support searching by coordinates.

Sharing: I’d show you the Live Maps views, but there’s no way to link to them. Not that I can find, anyway.

Another fair criticism. The workaround is to click Sharing -> Send in email. This launches a mail client with a new message containing the URL:

http://maps.live.com/default.aspx?v=2&cp=r18mqy92dxp9&style=o&lvl=1&tilt=-90&dir=0&alt=-1000&scene=3327738&encType=1

It turns out that you don’t need the default.aspx, and it seems that the minimal working version of that URL is:

http://maps.live.com/?v=2&cp=r18mqy92dxp9&lvl=1&style=o

(The backstory on the URL syntax is here.)

The cp parameter is the map’s center point, and I’m not sure how Live Maps computed the r18mqy92dxp9 in the above URL, but you can also use lat/lon coordinates in decimal form, so a more human-writeable form of the URL is:

http://maps.live.com/?v=2&cp=42.257500~-71.028889&lvl=1&style=o

So it’s doable. And to Doc’s point about lock-in, I’ve done this whole exercise in Firefox on a Mac, so there’s nothing Windows-specific going on here.

But he’s right. I shouldn’t have to work so hard to find, and link you to, the very cool bird’s eye view of the WUMB transmitter.

In response to this item and its follow-on discussion, Alf Eaton shows how you can, in fact, discover the (open access) scientific commentary surrounding an (open access) scientific article. Outstanding!

Here’s the interactive version of the service. You can feed it an URL, a DOI, or a PubMed id, and it fetches conversations about that item from Postgenomic, PubMed, Connotea, and Scopus.

I took the liberty of converting this service into a bookmarklet which I’ve labeled sc (scientific conversations). It’s the analog to my standard dc bookmarklet (del.icio.us conversations) and bc bookmarklet (bloglines conversations).

WordPress won’t let me post javascript: URLs so I can’t post the installable versions of these bookmarkets, but here they are in textual form:

sc: javascript:location.href=’http://scintilla.nature.com/conversations?uri=’+encodeURIComponent(location.href)

dc: javascript:location.href=’http://del.icio.us/url?v=2&url=’+encodeURIComponent(location.href)

bc: javascript:location.href=’http://bloglines.com/search?q=Bcite:’+encodeURIComponent(location.href)

If you make a new bookmarket, edit its properties, and copy one of these javascript: thingies into the URL or Location box, you’ll be good to go.

So, this is great! Now if I’m visiting a PLoS Medicine article I can just click dc, bc, and sc to assess how both the general-interest and scientific communities are reacting to it.

Thanks Alf!

I was in Montreal on Saturday to give a talk at CUSEC 2008, a great conference that’s organized by Canadian software engineering students (and recent grads) who want to congregate, exchange views, and hear from speakers they think will provide useful insight.

I gave the morning keynote, and Jeff Atwood spoke in the afternoon. Our messages dovetailed in an interesting way. Jeff’s title was: “Is writing more important than programming?” As a wildly successful blogger, the influence of his own writing has eclipsed the influence of his programming. He admits that this result is “not typical,” but argues that every programmer will reap benefits from narrating the work: influence, collaboration, clarity of thought.

My title was “Hacking the Noosphere”. The themes are shared tools and data, social engineering, language, the semantic web, human augmentation, and Doug Engelbart’s vision of the true purpose of information technology.

Although I’m trying to be more extemporaneous these days, I had a lot I wanted to say, and I wanted to say it carefully, so this turned into one of those talks that I wrote out completely. The upside is that I can make it available to read.

When chatter in the mainstream media and in the blogosphere intersects with scientific discourse, I’m always interested in the ways that citations do, or don’t, cross the border between those domains. In 2006, for example, while checking references for a podcast with Steve Burbeck about multicellular computing, I traced a meme about how we humans are really a hybrid of human and bacterial cells. The mainstream vector was a New York Times magazine story on obesity. It got to the blogosophere by way of a Wired News story. But the original Nature Biotechnology article mentioned in the Wired story was linked nowhere that I could find.

A comment from Gordon Mohr on yesterday’s item about Many Eyes prompted a similar analysis. Gordon asks:

…do the Many Eyes founders consider the statistical paradox that when testing large numbers of hypotheses, *most* recognized ’statistically significant’ results may in fact be false?

A good discussion of the issue is here:

http://www.marginalrevolution.com/marginalrevolution/2005/09/why_most_publis.html

To answer Gordon’s question, I don’t know, it didn’t come up in our conversation. But lets look at the conversation surrounding the PloS Medicine article cited in the blog entry to which Gordon points.

The blog entry itself was widely noticed, it has 31 del.icio.us bookmarks. What about the PloS Medicine article cited in this popular blog entry? It has only 6 del.icio.us bookmarks.

This is the URL cited by the marginalrevolution blog:

http://www.pubmedcentral.nih.gov/articlerender.fcgi?tool=pubmed&pubmedid=16060722

It’s not the most canonical form of the article’s URL. A more canonical form would be the base PubMed record:

http://www.ncbi.nlm.nih.gov/pubmed/16060722

That URL has 0 del.icio.us citations. However, now we cross over into the realm of scientific discourse. When you visit that PubMed URL, you’ll discover citations in the PubMed domain:

Comment in:

PLoS Med. 2005 Aug;2(8):e272.

PLoS Med. 2005 Nov;2(11):e361.

PLoS Med. 2005 Nov;2(11):e386; author reply e398.

PLoS Med. 2005 Nov;2(11):e395.

PLoS Med. 2007 Apr;4(4):e168.

There’s another canonical form for the PloS Medicine article, by the way. It has a Digital Oject Identifier (DOI):

http://dx.doi.org/10.1371/journal.pmed.0020124

Interestingly, there is 1 del.icio.us citation for that DOI.

So, what did the PloS Medicine folks have to say about the claim in the cited August 2005 PloS Medicine article? Here’s an April 2007 reaction:

The mathematical proof offered for this in the PLoS Medicine paper shows merely that the more studies published on any subject, the higher the absolute number of false positive (and false negative) studies. It does not show what the papers’ graphs and text claim, viz, that the number of false claims will be a higher proportion of the total number of studies published (i.e., that the positive predictive value of each study decreases with increasing number of studies).

I’m not interested here in the claim and counterclaim. I’m interested in the process of discourse, in citation as the engine of that discourse, in the role that canonical identifiers play in citation, and in the disconnect between scientific and mainstream discourse.

It’s all happening on the web, but it’s happening in isolated ghettoes with few points of actual contact. How could we bring those worlds into closer contact?

Here’s one approach that could help. When the citation engines in the blogosphere find references in blog entries to scientific articles on the web, they could resolve those to their most canonical forms: DOIs, PubMed records. And they could make equivalences among those forms. That way, conversation in the blogosophere about a scientific article, and scientific conversation about the same article, would tend to hang together and would be discoverable in the same contexts.

Why does this matter? Well, the marginalrevolution blog is influential, widely cited in the blogosphere. The entry that cited the PLoS Medicine article was itself widely cited. But the PLoS Medicine reaction to the article is not part of the blog conversation. I had to work really hard to find it, and to include it here.

The conversation-tracking tools used by bloggers should discover scientific discourse related to a scientific article as easily as they discover blog discourse. Conversely, the conversation-tracking tools used by scientists should discover blog discourse as readily as scientific discourse. Public understanding of science would improve, and so would scientific understanding of the public.

For this week’s ITConversations podcast I spoke with Fernanda Viégas and Martin Wattenberg about Many Eyes, a project at the forefront of a new category called social data visualization. I was particularly interested to hear about how civic or political argumentation, which tends to devolve into posturing — especially online — might improve when it’s grounded in shared data.

Martin
I don’t think we’ve reached data analysis utopia, but there are intriguing first steps. We’ve had a couple of solid political arguments happen on the site, where someone will put up a vehemently argumentative piece, saying for example that they believe people on welfare get too much money, and they’ll point to their statistics and charts to support that. In the skirmish that follows, people often get beyond the standard red-state/blue-state divide because it is rooted in the numbers.

Of course this argumentation doesn’t happen only on the Many Eyes site. Because the visualizations are linkable and (now) embeddable, it spills over to blogs as well.

I’m also intrigued by the notion that, as more people spend more time investigating official sources of data, we’ll start to uncover problems with the quality of that data.

Fernanda
We’ve seen that people have found mistakes on official data sets from authoritative sources. And the reason they were able to do that so easily is because visualization will show you something you didn’t have time or patience to discover in a spreadsheet.

This does leave Many Eyes open to the criticism that it invites people who lack statistical expertise to draw fallacious conclusions.

Martin
We’ve certainly run into objections that visualization can be deceptive. People are afraid that visualizations will be created that are inappropriate and misleading. And in fact that’s a well-founded objection in some ways, because every visualization is a simplification of the underlying data. There’s a point of view involved, and people are suspicious of that. But my belief is we have to give people as much power as we can.

Fernanda
Also, even though we created Many Eyes for the lay person, because we felt that this was something that was needed, that there was nothing out there for people to play with in terms of interactive visualization, it seems to be powerful enough to attract scientists too.

I think that kind of cultural mashup will be really good for everyone involved. Fernanda talked about how, at one point, a user put up a visualization of the Alberto Gonzales testimony that highlighted lots of “I don’t recall” kinds of statements. An hour later, another user put up a similar visualization of Bill Clinton’s testimony about Monica Lewinsky.

Fernanda
You could see the same sorts of phrases. The really exciting part, to us, was a couple of things. One, there was a conversation going on through these visualizations. Also, people usually think of informational visualization as this neutral tool, because it is based on data. Part of what people are beginning to understand, hopefully, is that visualizations have a point of view.

It’s been a decade since Tim Berners-Lee wrote Hypertext Style: Cool URIs don’t change, the first contribution to what is still not a very extensive literature on designing namespaces for the web. Recently, when I made the suggestion that a blog engine ought not produce URLs that end with .aspx, I was asked: “Why does it matter?” For me it boils down to two reasons:

1. Futureproofing
   A blog posting is, in theory, a permanent artifact. You’d like its URL to remain constant. Sometimes, of course, change is unavoidable. URLs aren’t digital object identifiers, and for most web resources, there’s no way to insulate yourself from an ownership change that results in a domain name change. But you don’t want to subject yourself to avoidable change, and file extensions fall into that category. Last year foo.asp, this year foo.aspx, next year something else, the only meaningful part of the name is foo. The technology that produces the name, never mind the version of that technology, is a variable that need not, and should not, be exposed. If links are pointing to foo.asp, and your upgraded blog engine produces foo.aspx, you broke those links. That’s unnecessary and avoidable.

2. Style
   Names without extensions are cleaner and simpler. Why does that matter? I guess if you think of URLs as constructs generated by machines for machines, then it doesn’t, because machines don’t care about style. But I believe that even when they’re machine-generated, URLs are for people too. We read, cite, and exchange them. Their structure and content conveys meaning in ways that warrant thoughtful analysis. Elements that don’t convey meaning, and that detract from clarity, should be omitted.

The Strunk and White Elements of Style for the literary form that is the web’s namespace hasn’t really been written yet, but Tim Berners-Lee’s 1998 essay belongs in that genre. So does the Richardson and Ruby book RESTful Web Services which, as I noted in my review, recommends that URIs use forward slashes to encode hierarchy (/parent/child), commas to encode ordered siblings (/parent/child1,child2), and semicolons to encode unordered siblings (/parent/red;green). We can, and we should, think and act in principled ways about the web namespaces we create.

I guess I’m extra-sensitive to the .aspx thing now that I work for Microsoft, because I know that to folks outside the Microsoft ecosystem it screams: We don’t get the web. It’s true there are plenty of .php and other extensions floating around on the web. But non-Microsoft-powered sites are far more likely to suppress them than are Microsoft-powered sites, because you have to go out of your way to get IIS and ASP.NET to do that.

Happily, that’s changing. The URL rewriting capability that’s long been standard in Apache, and is integral to modern web frameworks like Rails and Django, is coming to ASP.NET. From Scott Guthrie’s introduction to the ASP.NET MVC Framework:

It includes a very powerful URL mapping component that enables you to build applications with clean URLs. URLs do not need to have extensions within them, and are designed to easily support SEO and REST-friendly naming patterns. For example, I could easily map the /products/edit/4 URL to the “Edit” action of the ProductsController class in my project above, or map the /Blogs/scottgu/10-10-2007/SomeTopic/ URL to a “DisplayPost” action of a BlogEngineController class.

I hope that cool URIs will become the default for Microsoft-powered websites and services. Meanwhile, there are a variety of add-on URL rewriters for IIS that can streamline and normalize web namespaces. I wish they were used more extensively.

My longtime correspondent Raymond Yee, who I finally got to meet when I visited Berkeley last year, is writing a book on remixing data and services. The book mentions my elmcity.info experiment but, when Raymond visited the site the other day, all he saw was the text of the FastCGI script that runs the whole show. It turns out that when BlueHost upgraded Apache, they broke the mechanism that’s used to invoke arbitrary FastCGI scripts like my Django launcher.

It’s fixed now¹, but the incident reminds me that I haven’t yet fully developed the line of thinking that I’ve now tagged servicemanagement. What I am increasingly feeling, as I’m sure many others are — and not only geeks, but also and especially civilians — is that it’s becoming impossible to sanely manage and control our growing numbers of service relationships.

That lack of control was the real point of my Verizon story, for example. And my story is tame compared to this one from John Halamka, which begins:

On Thursday, December 20, my FiOS internet/TV service was shut off by Verizon without any notice or warning.

and concludes:

As CIO of Harvard Medical School and CareGroup, I spend millions every year with Verizon and I cannot navigate Verizon Customer Service.

One aspect of the service management console I envision here would be a common view of all the services I depend on, green/orange/red for healthy/sick/dead.

In the case of a website, it’s not enough to know that the box (or webserver) is alive, healthy means delivering the expected page. There are a million ways not to, and so in the past — although not in this case — I’ve used a cache-and-compare method to verify. It would be entirely feasible for a web hoster to wrap a user-friendly interface around that method, so that anybody could easily declare expected outputs, but I haven’t seen this done by a commercial hoster.

Of course every service relationship sets up expectations, so there are all kinds of assertions you might want to make. I received the e-bill by the expected date. My paycheck was deposited. The payment I made was credited to the right account. The package I sent was delivered. The book I returned to the library was received and checked in.

I want a common way to make all these assertions, and to subscribe to notification of assertion failure.

I’d also like my personal service management console to be subscribed to streams of events, from service providers, about the operation of their services. The expiry notice from EZPass, the Apache migration email I may or may not have received from BlueHost, the WordPress upgrade notice that’s only visible when I log in to WordPress — every time I turn around, another of these alerts pops up, but they’re all coming at me in different contexts, and through different channels. It feels scattered and random because it is. But logically there’s just a handful of communication patterns — like event notification, assertion failure notification, and upgrade/renewal confirmation — that could be abstracted into a common interface. As services multiply, and as their management friction increases, the need will become more apparent.

¹ Fixed for me, thanks to a specific intervention, but not, I observed and the BlueHost support guy confirmed, for others who wish to map arbitrary FastCGI scripts by declaring handlers in the control panel.

The always-interesting Jeff Jonas wrote recently about outbound record-level accountability, i.e., tracking where sensitive data is sent.

Without outbound record-level accountability … ensuring data currency across information sharing ecosystems can be problematic. The challenge being when a record changes in the originating system, how will one be certain which recipients of the original record need to be notified?

He adds that while such accountability is desirable, “not every mission will warrant the cost.”

I wonder, though, how much of the cost might evaporate if we make the architectural shift from sending data around, like email, to publishing it, like blogging.

I love the phrase data blogging, which Gavin Carr coined in response to some of the articles in my hosted lifebits series. One of the things that falls out naturally, in a syndication-oriented architecture, is the ability to audit who your subscribers are, and which chunks of data they access.

Note also that Jeff’s caveat about “which recipients of the original record need to be notified” implies owner-initiated push. But if the recipient is a subscriber, that update channel is already open and ready for use.

In terms of the value that the syndication pattern can provide, both for inter-personal as well as for cross-organizational communication, I think we’ve hardly scratched the surface.

On Saturday I’ll be in Montreal giving a talk at CUSEC, the Canadian University Software Engineering Conference. It’s an unusual event, organized by and for students. According to the backstory, the goal was:

…to bring the most passionate software engineering students from across Canada together under one roof, to listen and learn from the smartest and the greatest software engineers the world has ever seen.

As another of this year’s speakers, Tim Bray, has noted, we are in excellent company. Of course I’m not really a software engineer, and I don’t even play one on TV, but I’m glad that the planners thought my own unusual perspective would be valuable, and I’m looking forward to hanging out with a crowd of passionate students.

For this week’s ITConversations show I spoke with fellow Keene resident Neil Giarratana, a software entrepeneur whose 12-person company reverses the usual geographic pattern. A number of folks around here, me included, operate as remote outposts of companies located in metropolitan areas. But Neil’s company, Lucidus, is headquartered here, with field offices in larger cities elsewhere.

In an era of accelerating migration to cities, this counter-cyclical pattern fascinates me. As Neil candidly admits, there are tradeoffs. But thanks to ever-improving telecommunications and the evolving decentralization of work, it’s feasible to combine a high-tech career with the lifestyle advantages of our quintessential New England town.

In a tech industry that is obsessively if not pathologically dedicated to the Next Big New Thing, it’s hard to make the case for refining, reinterpreting, and consolidating what we already have. Bill Buxton does so eloquently in a recent BusinessWeek column, The Long Nose of Innovation, which I found by way of Kevin Schofield. You may recall Bill’s name from this introduction to our podcast interview about his book, Sketching User Experiences. In the BusinessWeek column Bill writes:

The heart of the innovation process has to do with prospecting, mining, refining, and goldsmithing. Knowing how and where to look and recognizing gold when you find it is just the start. The path from staking a claim to piling up gold bars is a long and arduous one.

That resonates powerfully with me. I’ve always been a prospecter, miner, refiner, and goldsmith who finds new value in mature technologies like NNTP conferencing, HTTP GET, and screencasting. Bill goes on to say:

Any technology that is going to have significant impact over the next 10 years is already at least 10 years old.

We might quibble. Was the web 10 years old in 1997? Yes and no. But I’ll grant poetic license because I think the statement is mostly true, and I’ve been wrestling with some of the consequences that flow from it.

Here’s one. Advocates for powerful ideas and methods that are long extant but have yet to fully bear fruit may tend to become nostalgic, appear misguided, act bitter, lose focus. These are counterproductive behaviors. So how do you avoid them? How do you stay the course, keep your eye on the ball, move forward, remain excited, and find ways to explore the same old things in new and different ways?

One answer, I think, is to keep engaging with different people in different contexts. Yesterday I was showing and discussing some things that I’ve known for so long, and documented so extensively, that I worried about sounding like a broken record. But in that context it was fresh information, a new perspective. People got excited. And their excitement rekindled my passion.

I finally got around to reading Michael Pollan’s excellent The Omnivore’s Dilemma which traces several different food chains from source to prepared meal. As I’ve mentioned here before, a remarkable follow-on dialog took place beween Pollan and Whole Foods’ CEO John Mackey, in the form of a blog exchange and a joint public appearance. That dialogue, which explores the book’s critique of “industrial” or “big” organic operations, is a great example of how in the blog era a book can sustain a lively follow-on conversation.

It’s a huge book, and there are a number of other conversations that might spring from it. One I’d like to see would focus on the possibility of a more transparent food supply chain. It’s true that there’s much about that supply chain we’d rather not know, but it’s also true there’s much that we simply cannot know. As service-oriented information systems increasingly control the supply chain, that knowledge — of how food is produced, processed, and transported — becomes, at least in principle, more discoverable.

The same applies more broadly to all supply chains. When Jeff Bezos spoke at MIT last year, several different folks asked variations of the same question: Can you expose more information about the production and transportation methods employed by the makers of your products, so we can factor those into our decisions?

Unlike government data, which is nominally ours, most corporate data is not something we’re obviously entitled to. Governments might compel a certain level of supply-chain transparency. Corporations with good stories to tell about ethical/sustainable practices might reveal them voluntarily. One way or another, we may begin to expect that supply chains ought to be more transparent than they are today.

In the case of our food system, making the supply chain more transparent would be a radical innovation — painful, but health-promoting.

When Verizon recently and erroneously canceled the online bill presentment service that I’d signed up for, I told them to just start sending paper bills again. I just couldn’t face the hassle of repeating their signup process.

For me, paper and electronic bills converge on the payment screen of my bank’s online service. So while the e-bills save me typing in amounts, versus clicking on a payment option, there aren’t many amounts to type and it’s really not a big deal.

I chose this method because, again, I couldn’t face the hassle of signing up individually for a bunch of per-biller payment systems. One obvious conclusion is that the long-awaited user-centric identity technologies now emerging — OpenID, CardSpace, and more broadly the identity metasystem — will grease the wheels, eliminate a huge amount of friction, and hugely accelerate e-commerce. If we think it’s big now, we ain’t seen nothing yet.

But beyond the convenience of single sign-on, and of common registration profiles that we can transmit with a click, a deeper issue looms on the horizon. It’s not just the psychic burden of signing up for services that weighs on our minds. Increasingly it’s the psychic burden of being in many service relationships, each of which needs to be managed and monitored individually.

Consider, for example, the problem of renewing those relationships. Just yesterday, I was confronted with three different renewal scenarios involving WordPress, EZPass, and GoDaddy. In each case I had to locate and jump through a differently-shaped hoop. That kind of thing wears you down. It’s never easy enough, your past experience is always too remote to guide you in the present, and if you fail or just forget, the consequences can range from annoying to severe.

What you really want, of course, is a renewal policy. When you set up a new service relationship, you define the policy: Renew automatically, on request, or never. In my case, I’d make all three of those relationships renew automatically. That would mean that WordPress gets to take ten bucks from my PayPal account every year for domain mapping, EZPass gets to refresh the expiration date on my credit card, and GoDaddy gets to charge my credit card for domain renewals.

What would it take to be able to review and manage all of your service policies in one place? Enterprises, for whom the need to do that is much more acute than it currently is for individuals, have concluded that service-oriented architecture is the answer. The much-maligned WS-* bells and whistles, which seem so overblown for simple point-to-point interaction on the web, come into their own in a fabric of cooperating services governed by policy-based intermediaries.

I predict that as individuals find themselves embedded in more and more service relationships, and begin to feel the need to manage those relationships more sanely, one of the current distinctions between the enterprise and the “consumer web” will start to erode. We’ll find that we are all embedded in many service relationships. And we will all benefit from technologies that enable us to flow those relationships through management consoles.

It was great to see my interviews with Beth Kanter and Dick Hardt appear on the ITConversations top 10 list for 2007. Since it’s the listmaking season, I want to make one as well. Not a list of favorites, because there are so many, but instead of conversations that best exemplify the theme of using technology in socially innovative ways.

Last summer I realized that this theme had become really important to me. It also occurred to me that, while there hadn’t been much overlap between ITConversations and its sister channel, Social Innovation Conversations, there should be. Doug Kaye and Phil Windley agreed, and I was delighted when my interview with Ned Gulley became my first crossover show to appear on both channels.

I think that many of my shows, including the interviews with Beth Kanter on working with digital immigrants in non-profit organizations, and with Dick Hardt on user-centric identity, touch on the theme of socially innovative uses of technology. Here’s a rundown of some others, in alphabetical order by last name.

Barbara Aronson: Making medical research literature available online, at low or no cost, to poor countries. (blog)

Ken Banks: Using SMS to create communication networks in Africa and other places ill-served by the Internet. (blog)

Gardner Campbell: Using the tools and methods of Web 2.0 to reimagine higher education. (blog)

Mike Caulfield: Bootstrapping and running a state-level community-based political blog. (blog)

Brian Dear: Enabling performers to measure and respond to demand for personal appearances.

Greg Elin: Extracting, reformulating, and making sense of the operational data of government. (blog)

Beth Jefferson: Federating the online catalogs of public libraries, and pooling the participation of patrons. (blog)

Ned Gulley: Designing problems to be solved by gameplay that teaches advanced skills using an optimal mix of cooperation and competition. (blog)

John Halamka: Modernizing the exchange of health care information, and putting patients in charge of it. (blog)

Timo Hannay: Bringing the tools and methods of Web 2.0 to the scientific world. (blog)

Ed Iacobucci: Creating a decentralized alternative to the hub-and-spoke air travel system. (blog)

Doug Kaye: Helping volunteers capture and publish audio recordings of civic events. (blog)

Matt MacLaurin: Recapturing the joy of creative expression in software, in a game inspired by LOGO and implemented using modern software principles. (blog)

Hugh McGuire: Bootstrapping and running a collective effort to record and publish public-domain audiobooks. (blog)

Simon St. Laurent: Chronicling the civic and political life of a small town. (blog)

Jim Russell: Analyzing the dynamics of the Pittsburgh diaspora. (blog)

Greg Whisenant: Enabling cities and towns to publish crime data online, and imagining the citizen/government collaborations that can flow from that. (blog)

John Willinsky: Advocating open access to academic literature, and reimagining education in the era of Net participation. (blog)

Jeannette Wing: Explaining why the principles of computational thinking will become part of everyone’s educational foundation. (blog)

On a recent flght to Seattle, Microsoft identity expert Vittorio Bertocci wrote:

I want to take some time writing down some hallucinatory (=vision without execution) thoughts about omnidirectional identities. Be warned, this may be just pointless rambling.

It isn’t pointless, not by a longshot, but the term omnidirectional identity needs to be unpacked — and maybe even revised to something like public (versus private) identity, or broadcast (versus narrowcast) identity. I had a long talk with Vittorio last month, for a new interview series I’ll be launching soon, and in the part where we discussed OpenID and CardSpace he discussed omnidirectional and unidirectional identity:

VB: OpenID is actually a kind of omnidirectional identifier, which is something that sooner or later we have to deal with. Whereas cards are metaphors that help me to do things that are unidirectional. Every time I use a card, it’s for a transaction specifically with one relying party.

The same happens with OpenID, but you have the perception that there’s a URI which describes you. This opens the way to future developments which, in my view, we desperately need. What we see happening with Facebook is just a signal that the industry needs to do for omnidirectional identifiers what we are now doing for unidirectional identifiers.

JU: Can you define those terms?

VB: The idea is that your identity, or identity in general, can have different audiences. An omnidirectional identifier is something you use for being recognized by everybody. So if you go to the Verisign website, using HTTPS, their certificate declares their public identity.

Then you have unidirectional identities. So if I land on a website that, for business purposes, asks my age, then I obtain a token specifically for that website. We call this unidirectional. The flow goes straight to that website and nobody else. When you use a card today, or OpenID, you’re in a unidirectional context. You’re transmitting attributes to one specific relying party.

But in the case of OpenID, I have my account, vibro.openid.com, and it’s a URI, it’s my identifier, and it’s omnidirectional in the sense that everybody knows it. While in the case of my cards, there’s nothing that I tell to everybody. So I think OpenID is a good starting point for thinking about an ecology of omnidirectional identity. How do I handle identity that I want projected everywhere, not just to a specific relying party?

Also, the concept of an identity provider — in both CardSpace and OpenID — is for giving you attributes about yourself. I go on a website, I want to buy wine, I am the one who is asking the identity provider to certify me. While in the world of social networks, the requester of an identity may be somebody other than me. If somebody is looking at my profile, it’s not me. But the request is still for identify information about me. This is an area that needs thought. As an industry we did an excellent job with unidirectional identity, and the ecosystem for both CardSpace and OpenID is vital. But we haven’t yet found the laws for omnidirectional identity. When we do, things like Facebook Beacon won’t happen. We need to extend the conversation to include omnidirectional identifiers for users. A website has a public identity. But at this moment, a user’s public identity is an imagined phenomenon. You search for yourself and find traces of your identity on the web, or maybe the identity of somebody who has your same name.

JU: Or someone who said something about you. Made a claim about you, in effect.

VB: Exactly.

I’ve long projected a public identity omnidirectionally, so I’ve had a long time to consider this issue. A decade ago, when I realized the asymmetry of digital certificates — the secure website identifies itself to you, but not vice versa — I began using, and advocating the use of, client digital certificates. I used them to sign my emails, and would have used them to sign my postings to the Net if there had been any kind of ecosystem in place to recognize and honor those assertions of identity. There wasn’t, and there still isn’t. Meanwhile, as Vittorio notes, we’ve done a good job of first thinking through, and then implementing, the unidirectional identity scenarios that we need for e-commerce.

I realize now that even blogging, as big a phenomenon as it has become, wasn’t enough to motivate serious thought about the kind of public identity projection that I’ve always understood blogging to be. But I think Vittorio is right. The social networks are a much bigger phenomenon, and they’re acquainting many more people with the notion of public identity projection. Perhaps now the need for a system that enables people to project and manage their own public identities — a need that I was never able to articulate convincingly before — will simply become apparent.