As I lay in bed this morning, in a sleepy haze, NPR whispered sweet nothings in my ear about the G-8 Summit and presidential tummy aches. My thoughts drifted from polonium-210 to Putin to Bart Simpson in the "I didn't do it Kid" episode to Russian-based denial of service attacks on server clusters in defenseless little Estonia, to the inefficacy of US missile defense systems in Poland to defend against such threats in "the cloud", to Native American Rain Dances, to the methods by which developer API programs have been successfully "seeded" in the past, to the ethics of intellectual property protection and open innovation and defensive patent portfolios in the age of information and then, peacefully, I drifted back to sleep.

When I awoke, sometime later, I was grasped by a thought, 'I wonder if someone has taken out a patent on how to seed a rain cloud.' I stumbled into my dining room, cracked open my laptop, and dialed up a Patent Search on the United States Patent Office Web site. Eureka!

Method of Cloud Seeding - Graeme K. Mather (1992)

Is that not the coolest patent title ever? I have GOT to get me one o' those. Related patents (below) abound because...when it rains patents, it pours patents.

And to bring this full loop back to missiles...here's another cloud seeding patent, sponsored by the United States Navy (duh!), A weather modification cartridge dispenser for automatically igniting and spensing pyrotechnic weather modification rounds wherein the dispenser is basically a motor driven automatic spring powered gun.

I am tickled pink 'n honored to announce the third release of Microsoft Tagspace*, a social bookmarking solution for technical professionals, like you. With this release, Tagspace becomes Microsoft’s first true social bookmarking application for the whole World Wide Web Web. Learn more about Tagspace and its potential to help you save, recall, and connect to the people, subjects, and Web-based resources that matter most to you here.

With today's release, you can now use Tagspace to:

• Tag Practically Anthing on the Web--Apply tags to practically any site on the World Wide Web, excepting those that are known to contain offensive, malicious, and otherwise inappropriate content.
• Browse Member Tags--See what other users have tagged and view their personal tag clouds, by clicking on their display names.
• "Tag Drafting"--Subscribe to the RSS feed for a tag (like tagspace).
• "Member Drafting"--Subscribe to the RSS feed for other members' public tagged items (my Tagspace RSS feed here;-), by clicking on their names and subscribing to the RSS feeds associated with their tagged items lists. 
• "Tag Drafting" and "Member Drafting" are excellent ways to stay up to date, diminish information overload, and approach what I like to call "domain omniscience", at little expense to yourself.

Kudos to Taylor, TShak, Marshall, Huong and everyone else on the CDS team (including Dave, the Other Dave) who contributed to the successful development and deployment of this precedent setting release. You exceed exceptions, exceptionally.

*This is a Beta release. You can expect more pleasant surprises from the Tagspace team, especially if you're a software professional who digs social bookmarking tools, in the near future. Stay tuned and Chime in, because we'd love to hear your ideas for how we can improve Tagspace even more.

Ted Haeger, aka ReverendTed of Bungee Labs (purveyors of the most kill-killski development toolkit for Web 2.0 developers, in the world), just published a thought provoking blog post asking his readers: Can we...?

Trust Microsoft with Claimspace

Ted has personally challenged me to respond and I plan to do so, in the next couple of days. In the meantime, I encourage you to check out Ted's post and weigh in with your thoughts and opinions, either here or there.

Clay Shirky recently published a post on Corante, entitled "Against Well-designed Reputation Systems (An Argument for Community Patent)" that I've been meaning to respond to, for awhile. His thesis, which I agree with wholeheartedly if I understand it correctly, can be summed up as 'Don't do it. Don't even think about doing it.'

Clay, rather than respond to your post with a post, I will instead respond with a working implementation of an alternative approach to social evaluation (same ends...different means). Due out in alpha in the next few weeks, I believe that Claimspace demonstrates my agreement with your observations and reservations about the risks inherent in developing a traditional ranking and reputation system. Claimspace speaks louder than words. It may even prove useful as a social evaluation platform for community patents.

A favorite passage from Clay's post:

"The obvious conclusion to draw is that, when contemplating the a new service with these characteristics, the need for some user-harnessed reputation or ranking system can be regarded as a foregone conclusion, and that these systems should be carefully planned so that tragedy of the commons problems can be avoided from launch. I believe that this conclusion is wrong, and that where it is acted on, its effects are likely to be at least harmful, if not fatal, to the service adopting them.

There is an alternate reading of the Slashdot and eBay stories, one that I believe better describes those successes, and better places Community Patent to take advantage of similar processes. That reading concentrates not on outcome but process; the history of Slashdot’s reputation system should teach us not “End as they began — build your reputation system in advance” but rather “Begin as they began — ship with a simple set of features, watch and learn, and implement reputation and ranking only after you understand the problems you are taking on.” In this telling, constituting users’ relations as a set of bargains developed incrementally and post hoc is more predictive of eventual success than simply adopting any residue from previous successes.

As David Weinberger noted in his talk The Unspoken of Groups, clarity is violence in social settings. You don’t get 1789 without living through 1788; successful constitutions, which necessarily create clarity, are typically ratified only after a group has come to a degree of informal cohesion, and is thus able to absorb some of the violence of clarity, in order to get its benefits. The desire to participate in a system that constrains freedom of action in support of group goals typically requires that the participants have at least seen, and possibly lived through, the difficulties of unfettered systems, while at the same time building up their sense of membership or shared goals in the group as a whole. Otherwise, adoption of a system whose goal is precisely to constrain its participants can seem too onerous to be worthwhile. (Again, contrast the US Constitution with the Articles of Confederation.)"

The Backstory
Dr. Credlove, How I Learned to Stop Worrying and Love the Reputation System

Last year, after we launched CodePlex, I sat down with my new manager, Bob Rebholz to discuss what my next big challenge at Microsoft might be. Bob was busy planning the overall strategy for project "Athens", which would come to be known as Microsoft.Community, internally. To his credit, Bob gave me a lot of freedom to chart my own course. But one thing he insisted upon was that I assume product management/planning for a  project he had in mind to 'do something about reputation and recognition.' Alas! Reputation! What better than the frickin' Holy Grail of Social Computing to keep me stimulated and gainfully employed for years to come? I wanted it but I hid my eagerness behind a veil of resistance. People DIE when they touch the Holy Grail, right? That or they go insane trying to find it. Why in the world would I accept the charter to build a ship that might never sail, of its own power, or drive me crazy, in the process? Did I really want to perish like all those crazy Nazi dudes in Indiana Jones. NO!

For nearly two weeks, I tried to convince Bob to unload "Reputation" on one of my two peers, Dave or Brian. But Bob was resolute and frankly, I'm drawn to challenging v1 products like a moth to flame.

To take a bit of the sting out of ugh, "reputation", I soon prevailed upon my new teammates to adopt the kindler and gentler approach and code name: "Rapport", for our fledgling project. I then focused my attention on defining and delivering on two objectives:

1. Enable technical professionals to gain recognition, on their terms, wherever they go on the Web.
2. Enable people to rapidly ascertain and socially evaluate the probable credibility of any online resource whose author has included it in Claimspace: a placeless market of opinion.

"Hm?" you ask, "Isn't credibility sorta related to reputation?" Well, yes. Yes it is. But it is not the same thing. Wikipedia's entries on reputation and credibility are illuminating and um, confusing. I have toiled, perhaps overmuch, to convince my team and indeed, anyone who would listen that building a traditional, point-based "reputation system" (like Slashdot's karmic system) is a dangerous and costly proposition. I even developed a handful of little slogans to drive my anti-Reputation crusade, such as "REPUTATION IS THE ONLY FOUR-LETTER WORD IN THE ENGLISH LANGUAGE THAT HAS MORE THAN FOUR LETTERS."

The central points in my anti-reputation argument were threefold.

1. If you build a traditional reputation system, users will "game" it, meaning that success will come at a steep and continuing cost, both in terms of dollars and user acceptance. 
2. It is dangerous for a company to assign a value to its customers. Doing so is bound to alienate more customers than it delights.
3. Reputation is a personal and subjective calculation of a person or group's probable behavior or reliability or credibility, in a specific context or situation. The measure of a person or group's reputation cannot be reliably expressed, in a simple and universally meaningful way because the context and personal objectives of the subjects and their evaluators are ever-changing. For example, consider this well-known photo and fill in the blank.
   
   In the context of the Yalta Conference, Joseph Stalin's reputation was one of _____. On a scale of 1-10, Stalin had a reputation of _____? On what basis? To whom?

Interestingly, it is possible that Claimspace--or something similar--might someday be used as the basis for an entire generation of reputation systems. Funny how things work out, isn't it, Bob?

Robert Rebholz is not only my boss*, he is also my muse, ideological sparring partner, alter ego, and mentor. Bob is possesed by a special kind of genius, with a sort of Jeffersonian breadth and intensity that makes it a pleasure and honor to collaborate with him, on a day-to-day basis. In my opinion, Bob is one of two people on Earth who can talk about the BIG idea that is Claimspace, with absolute confidence, competence, and credibility. If you have even a passing interest in online communities of practice, folksonomies, reputation systems, credibility, identity, recommendation systems, rewards, "flow", collaborative filtering, "social search", & related areas, I encourage you to subscribe to my RSS feed and Bob's RSS feed.

Yesterday, Bob posted an excellent post about Claimspace that wades into the broad river of uses that it might one day support, for both users and "community owners", across the Web. He cites the following potential uses:

• "Long tail recognition system"
• Solution to the "Who can I trust? issue"
• "Generalized polling mechanism" (and portable)

• "A simple REST API gives everyone (and I mean everyone -- the mashup possibilities are just staggering -- caveat, keep the crawl, walk, run idea in mind) the ability use the data in a manner best suited to their needs: community (MVP or other influencer) reward programs, product design input, product feature voting, bug prioritization, and on and on and on, all without a ton of custom code. Any Digg-like application would love this kind of data. Can you imagine -- hottest claims, hottest people making claims, most used claims, newest claims, by product, by solution area, by geographical region, and the list goes on."

• Lastly but not leastly... Bob identifies the possibility of using Claimspace as a bizarro substitute for a traditional, taxonomically hobbled, binary choice or n-scale rating system, which he describes thusly: "Claims can be created and applied by anyone, including the people hosting the community. They could be built right into the forums application, for instance, to support assertions or claims such as "was this post helpful", or "this post answers the question asked". A library team could, for instance, create several standard claims (a claim/assertion taxonomy) that relate to the quality or usefulness of the posted library content."

Alas, it is true. Perversion will occur.

Alas, we must accomodate the taxonomy-doers and guide them to the right path, if we can. But Claimspace is a folksonomy.

Personally, I believe that the taxonomy-doers will come to see the futility of their ways and that if they don't, they will lose the vast majority of their customers, over time. For example, if Typepad disallows xClaims and Blogger allows them, Typepad runs the risk of making Blogger appear to be a much better blogging platform than it actually is, relative to Typepad ;-).

It's tempting and easy to impose one's way of thinking on others; to deprive one's minions or customers of the ability to control the means by which resources of their creation are published, organized, discovered, and evaluated by other people. The organization of information, access to publication mechanisms, and permission to cite, annotate, edit, and otherwise alter the organization or substance of information resources or its metadata, both online and offline has ALWAYS been closely and jealously guarded. Those who control "the tree" of information control you. The taxonomy-doers derive personal benefits from that control, often at our expense and often, in the absence of compensatory benefits. In many cases, taxonomies are indeed helpful. But Claimspace is designed and is being developed primarily as a "folksonomical" resource rating system. As such, Claimspace has the potential to be medium of social evaluation that empowers the little people: you, me and millions of other self-publishers, to gain recognition and evaluate credibility, on our terms, rather than in a way that is strictly and uniformly defined by AOL or Microsoft or O'Reilly or Yahoo or Google.

Are you subscribed to this blog?

*Note that this is the first time I've mentioned Bob, in my blog. Talking about one's boss in a public forum is tricky, both socially (wrt personal credibility) and from a career perspective. However, I feel that Bob's ideas deserve your recognition, as they command my attention and respect, and not just because he looks like Zod.

In coordination with Taylor Development, which among other things owns an undeveloped 60 acre parcel of land that is zoned Manufacturing Park (MP) along Union Hill road in Southeast Redmond (see Redmond zoning map here and Live.com Map here), City Staff has presented the Redmond Planning Commission, of which I am a presiding member, with a proposal to expand the list of permitted uses in Redmond's Manufacturing Park (MP) zone to include "Wholesale/Retail Membership" stores. In other words, they propose to enable folks like Mr. Paul Taylor with the flexibility to build a Costco or Sam's Club-type store out by the UPS distribution center, east of Target and Mervyns, in SE Redmond. To accommodate this, Redmond City Staff has proposed that we allow such uses in all the MP zone in SE Redmond. throughout the City of Redmond.

Correction, 5/8/2007: I have been informed that the proposed regulatory ammendments to permitted uses in the MP zone would limit wholesale-retail stores to the MP area in Southeast Redmond only.

What do you think? If you live in or near Redmond and especially if you commute through or live in or near to Southeast Redmond near a Manufacturing Park Zone here (to/from Redmond via Avondale Road, Redmond-Fall City Road, Willows Road, or other), I'd like to hear what you think about this proposal. I am one of the Planning Commissioners who will soon vote on whether or not (and why) the City Council should approve this proposed change. Your opinion matters to me. But more importantly, your opinion matters to your fellow residents and elected officials. As such, I encourage you to comment, on public record, by emailing your thoughts to Sarah Stiteler, with the City of Redmond. I'm sure that Sarah can also provide you with the full Technical Committee Report, which I can't find on the City Web Site (argh!), that outlines why City Staff believes this proposed change to be viable, appropriate, and legal.

The deadline for public comment is May 15, 2007 at 4:30PM.

The issues before the Planning Commission (and you) are complex...

• Service vs. Manufacturing--Do we need a major "wholesale/retail membership" store in Redmond? What do we lose, in terms of future capacity for manufacturing uses and employment that might evolve in the future, in Redmond, if we allow this change to existing regulations?
• Traffic and other Impacts--Is it wise or appropriate to place such a relatively high intensity land use in one of our MP zoned areas in Redmond, almost all of which are in areas where traffic and other impacts are already great?
• Individual vs. Public Rights--Is this the best or only way to provide for our land owners' constitutional right to capitalize on the value of their real estate holdings?
• Alignment with Redmond's 20-Year Vision--Is the addition of "wholesale/retail membership stores" to the list of permitted uses in Redmond's Community Development Guide in MP zones congruent with the vision of Redmond as articulated in our Comprehensive Plan? This is an all-important question because it is a necessary and legal precondition for approval of the proposed change insofar as the Development Guide is constructed from the fabric of the more conceptual and Comp Plan. So far, no changes to the Comprehensive Plan have been proposed... If you would like to dig into this very sticky subject, I encourage you to obtain a copy of the Technical Committee Report from Sara Stiteler and consult the Comp Plan "policies" and Development Guide "regulations" cited therein. Both of these documents are available, en toto, by clicking on the hyperlinks above. Unfortunately, I cannot easily point you to the specific policies and regulations, by URL. However, you can grab the ref #'s from the Tech Report and then easily search the online documents. Aw heck, just drop me an email or comment, if you cannot easily find your own way around. I'll be more than happy to assist in exchange for some direct and honest feedback.

Again, if you'd like to weigh in on this issue, please email your heartfelt comments, preferably with your name and address, to Sarah Stiteler, at the City of Redmond, or call her at 425.556.2469. For a copy of materials for the current meeting, or to receive weekly emails with Planning Commission meeting materials, please contact Daphne Harold or call 425-556-2421.

A few months ago, Alex Barnett excitedly told me about a project he was working on with Pablo Castro, of the Microsoft SQL Server team. Like most things brilliant and game-changing, their invention is shockingly simple. As Alex explained it, project codename "Astoria" would enable anyone to expose (and query/update) a SQL Server database, in the cloud, via a REST API...yup, simple URLs...over HTTP.

"Wait a second. Wait a second. Wait a second," I said, shaking my head and playing for time to catch up and catch on as Alex sat there, his eyes alive with creative energy. "Are you telling me your program allows me to query and potentially update a database in the cloud as easily as I can now query one directly, using my query editor? And my queries will be expressed with something like http://foo/bar/blah...?" He nodded, "Yes."

I GET it. I can REST.

Several weeks after our initial meeting, Alex and I sat down with Pablo, Taylor, Dave, and Bob to discuss the possibility of using a snapshot of our beta social bookmarking solution, Microsoft.Community Tagspace, as a sample dataset for the unveiling of Astoria, at Mix07. On Monday, Pablo did just that.

Ooooh, I feel like the cat presenting its prey to its favorite humans on their back porch...

Click Here, for more information about Astoria, examples using a snapshot of the Tagspace store, links to documentation, downloads, videos and, other goodies. Alex rocks.

NOTE: The Tagspace dataset to which the Astoria service points is NOT the live Tagspace database. For Tagspace, we are planning to expose our own REST API, with initially gated access and Read-only access, in the near future. Our initial REST implementation will differ, syntactically and significantly, from Astoria's. But you can bet you last two bucks that we'll be keeping a close eye on Astoria and continuously evaluating how we can leverage it to improve the data programmability model around Tagspace. To keep track of this and other Tagspace and Microsoft.Community developments and to weigh in with your valuable feedback, I encourage you to subscribe to this blog and comment, with abandon.

Are you a code monkey?
Do you dress like a code monkey?
Do you dance like a code monkey?

In response to my penultipate post, reader "David" (the other David?) xClaims: "Um, I don't get it - what's this for again? Is it a microformat or something? I hereby claim xClaims are confusing." My vote: Abstain + a Comment (below):

I hear you, David. And point taken. Note to Self: continue to refine messaging around Claimspace. Thanks for the feedback and keep it coming. As with any unreleased product and all true innovations (again, early June), it's hard to predict how folks will use Claimspace. Usage will drive the messaging. But for whatever it's worth, I *love* your first xClaim! And I point out that you just created the SECOND public xClaim, in history. ;-)

To your questions,

Question: "what's this [an xClaim] for again?"
Answer: An xClaim is an author-defined, reader interactive rating/polling mechanism for the Web that enables a person to assert that, 'I created this resource and I wish to be recognized personally or promote the recognition of my resource on these terms [my claim]. What do you think? Vote/Comment here.'

Question: "Is it a microformat or something?"
Answer: An xClaim is a control, not a microformat...yet. For my thoughts on the difference between a control and a microformat, see http://blogs.msdn.com/korbyp/archive/2007/04/12/microformats-are-like-rfid-tags-for-the-web.aspx. For any demonstration sites that we provide (Tagspace and Claimspace are being designed as services, first and foremost, for inclusion in other Web sites), we are super-interested in using existing microformats like rel, XFN, hCard, and hCalendar. For xClaims, in particular, we are currently investigating the extent to which we can use VoteLinks or whether we need to begin a conversation with the fine folks at microformats.org and elsewhere to explore a new microformat or extension of an existing one.

In early June, we will launch a new social software service for technical professionals called Claimspace (codename, "Rapport"), which will join Tagspace, Blogs, and Forums as the newest member of the Microsoft.Community family. Our development lead, Doug, mentioned Claimspace a few weeks ago so I figured I'd follow up.

Tagspace enables you to say, 'I found this resource and it appears to be worthy of my attention.'
Conversely, Claimspace will enable you to say, 'I created this resource, wish to be recognized for it on these terms ___, and I hope you find it worthy of your attention. What do you think?'

What is Claimspace, exactly?
Claimspace is a decentralized, folksonomical resource* evaluation and recommendation system for technical professionals. Claimspace will enable you to take credit for your great ideas and gain recognition for yourself and your valuable contributions, wherever you go**, on the Web. Claimspace will provide a structured and simple way to build social capital, quantify its value, and establish credibility, on your terms. To participate in Claimspace, all you have to do is create and deploy or respond to an xClaim, anywhere on the Web.

*In this context, a "resource" is any item on the Web that is URI addressable. Conceptually, we divide resources into two groups: static and dynamic. A static resource is a resource that does not change. Static resources include Web pages, podcasts, videos, & etc. A dynamic resource is representative of a resource that produces static resources. Dynamic resources include such things as people and RSS feeds. How is Claimspace "folksonomical"? You can write anything you want in an xClaim; absolutely anything. We're not your parents and we do not impose a claim taxonomy.

**In our first release, Claimspace will be usable only in the context of our new Blogs and Forums. 6-8 weeks later, we plan to extend support for the creation and deployment of xClaims on practically any Web page to which you have write access, on the Web.

What is an xClaim?
Claimspace will be powered by legions of interactive widgets, which you and other Microsoft.Community members scatter across the Web. These widgets, which we call xClaims, are portable polling stations that you will be able to create and paste into or alongside practically any blog post, threaded discussion, podcast, code snippet, photo, video, or anything else that has its own URL which you wish to be recognized for, anywhere on the Web. Here's an example of what an xClaim might look like, in the context of a blog post that I wrote a few months ago: Friend-o-Gen, for just $.99/month. This is a mockup and only a mockup. Since Claimspace is a service, the look and feel of xClaims will vary on a site-by-site and client-by-client basis.

In the xClaim mockup above, the 'up arrow', 'down arrow', '?', and other little icons constitute an interactive voting panel. xClaims have three core vote options: '+', '-', and 'WTF?' These vote options are client-extensible and can be rendered as anything, including text descriptions like 'aye', 'nay', 'abstain' by the client application.

Why participate in Claimspace?
xClaims will enable you to call attention to and provide your readers or viewers with an easy way to vote and comment on the statement your xClaim contains; your claim. After responding to your xClaim, members can visit Claimspace to see how other members responded (or the client site can pull down and display vote tally information, programmatically). They can also view a list of all claims that you have created over time and navigate to the Web pages where those claims are posted, if they want.

xClaims will not only dress up your online contributions, they will drive traffic to them! More importantly, xClaims are designed to give your readers the information they need (the recommendations of other members) to comfortably and confidently heed your advice, act on your good counsel, download your goodies, and otherwise consume the resources you so graciously provide, on the Web.

If you would like to harness the simple power of Claimspace to your personal benefit, here are a few ideas and examples of how you might use xClaims to your advantage...once we release;-):

• Blog and Forum Posts
  Read a few of your most recent blog and forum posts. If you don't yet have one, you can read this or this or this, instead. In each post, I'm betting that you'll find one sentence that articulates a central idea or thesis. This is the punch line. This is the meat. Everything else is supporting evidence. When you wrote your post, you may even have considered making that sentence bold or calling it out in some other way (e.g., "I'm going to make a catorical statement..."). When Claimspace is released, consider placing your meaty theses in an xClaim, instead. An xClaim is an IDEAL way to draw your readers' attention to the heart of your blog posts and other online content submissions and obtain laser-focused reader feedback and recognition for that which matters to you most.
• Aggregating Praise and Building Credibility, Across Multiple Venues
  Most technical professionals who participate in online communities participate in and contribute helpful resources to two or more online community venues. Sometimes, you post relevant and useful information on a blog. Other times, you answer questions on forums.microsoft.com. Occasionally, you pick some low hanging fruit and answer a recently posted question on tek-tips.com or another independent forum or newsgroup. Once or twice, you may even have posted photos of whiteboard diagrams on Flickr or Live.com and pointed to them from elsewhere. Wouldn't it be great if you could aggregate all of the "thank you" notes you receive across all of those venues and give future recipients of your assistance a sense of your credibility and trustworthiness. xClaims allow you to do just that.
• Code Submissions
  If you are a programmer, there's a 99.9% chance that sometime in the last week, you stumbled upon and considered copying and pasting or downloading and compiling a code snippet or set of source files from the Web, perhaps an entire open source project on CodePlex.com. But you hesitated, didn't you? You hesitated because you had no idea who the author was. You feared that the code might contain a line or two of GPL code that might create costly problems for you or your company, in the future. For all you knew, the author, "a8vs_hippo" may have laced the source file you considered re-using with malicious code. Wouldn't it have been nice if you could have learned more about a8vs_hippo's from other people who you know or believe to be trustworthy and "real". In the future, when you post a snippet to a forum, upload a sample to ProjectDistributor.net, or check in a changeset to CodePlex.com, we hope that you will consider associating an xClaim with it. If the only thing notable about your code is that "This code compiles," make that your claim. xClaims are good etiquette.

Claimspace is designed for technical professionals who want to:

• Reward and Be Rewarded
  Build social capital and reap the rewards. By associating xClaims with your technical contributions on the Web-your blog and forum posts, podcasts, code samples, diagrams, photos, videos and any other URI-addressable item-you will enable your readers to give you the running bear hug you deserve and increase the visibility and credibility of you and your valuable technical resources.
• Discover and Connect
  Tap into your social network. Claimspace will enable you to tap into the power of a vast social network of technical professionals on the Web who share your needs, interests, and concerns and who can point you to the resources you need to get the job done.
• Evaluate Credibility, Quickly
  Consume community resources with greater confidence. Claimspace will enable you to rapidly ascertain the probable credibility and relative value of many technical resources on the Web-people, blogs, forum posts, RSS feeds, etc-by consulting the vote tallies (and voters) of their associated xClaims.

Key features of Claimspace that we are planning to include, over time:

• xClaims
• Your name, picture, and member since [date]
• Your group affiliations (e.g., if you are a Microsoft MVP, your xClaim will be adorned with an "MVP" logo, if you want)
• Vote on claims
• Leave a comment
• Suggest a claim
• Subscribe by RSS to a claim by member or all members
• View xClaim Vote Tally for:
• A member's claim, for a particular URL
• A member's claim, across all URLs where they posted it.
• All of a member's claims (lifetime rollup)
• Member Directory
• Search and Browse Claimspace for claims, by keyword
• Tight integration with Microsoft Tagspace
• Tight integration with Microsoft Forums
• Tight integration with Microsoft Blogs
• REST API - Integration with your favorite community sites and services...

[xClaim placeholder]
Korby Parnell xClaims: "I created Claimspace."*
[xClaim placeholder]

I bet the developers and testers on the Rapport team wish they could take issue with this unilateral and egoistic claim, TODAY. Huahahaha. Ship it boys! Ship it! Whereas this claim is technically true, it belies the co-creative nature of any serious software development effort. Props to the core members of the Rapport team: Eric Mahlberg (lead dev), Jason McCullough (lead test), Ben Martin (cat herder in chief), and David Waddleton (dev). Special thanks to Bob Rebholz, who had the vision to spin up our project and plant the seed of "personal recognition elements", an idea which has grown into xClaims.

Tagspace* is a social bookmarking service for software professionals** that encourages sound sleep and sweet dreams by enabling you to be better informed, better connected, and more productive. The more you use Tagspace, the more you'll wonder how you survived for so long in the cramped quarters of your Web browser's Favorites folder.

WARNING: TAGSPACE IS ADDICTIVE. REPEATED USAGE MAY CAUSE INCREASED PRODUCTIVITY.
*Tagspace has been shown to be effective in helping to prevent and reduce memory decay.
**No animals or software engineers were harmed in the making or testing of Tagspace.

For more information about Tagspace, see:

Screencast (direct stream): intro2tagspace.wvx
Screencast (on MSN Soapbox): intro2tagspace.wmv
Text Overview: Tagspace Beta Refresh Overview
Product Roadmap: Microsoft.Community Today and Tomorrow  (...because this is just the beginning.)
Tagspace: In the News
Subscribe: RSS

Today, I took a much needed break to attend a Microsoft Research talk by Paul Dietz, who is a scientist at the Mitsubishi Electric Research Lab (MERL).

In describing one of his inventions, a system that automagically pings your waitress when your glass is half empty, Paul described RFID tags as a "passive, non-interactive component". He then proceeded to describe how he and his associates at MERL have figured out how to enable two devices to communicate using low cost LED lights, at hundreds of bits per second. But I'll get back to that, in a second.

Suddently, it hit me: a quick and simple way to describe microformats to my friends and colleagues!

A microformat serves the same function on the Web as an RFID tag in a Walmart warehouse! Microformats are descriptive but passive. They just sit out there and wait to be discovered by an interested agent. They are small and easy to miss, unless you're looking for them. Microformats, like RFID tags, talk to everyone.

What is a microformat? A microformat is an RFID tag for Web pages. Do you see any problems with this analogy?

Now, back to LEDs and Paul Dietz... I invite you to chew on this for a second:

LED a + LED b = communication medium

Think about the hundreds of LED lights that you encounter on a daily basis: on your keychain, desktop, dashboard, keyboard, remote control, auto, kitchen appliances, telephone, TV, computer, and even your kids. Paul Dietz is not just another Talking Head.

Someday, you may find yourself living with a cheap cell phone...
And you may find yourself, holding that cheap cell phone to the tail light of a large automobile...
And you may find yourself, uploading information about that large automobile to your mechanic...
And you may find yourself, connecting to the Web by opening your laptop under an LED light.
And you may ask yourself, "How do I work this?"
And you may say to yourself, "MY GOD, WHAT HAVE LEDs BECOME?"

Paul Dietz is an engineer who strives to create elegant circuits and systems that bring a smile and make the world a slightly better place. He is best known for his work on interactive systems including DiamondTouch (an identifying, multi-user touch screen), iGlassware (RFID-based, level-sensing glassware that automatically calls for refills) and Pal Mickey (a location-interactive plush toy sold at Walt Disney World). In his spare time, Paul runs the Animatronics Workshop – an extracurricular activity for kids 11-14 years old where they build complete robotic shows. He holds a Ph.D. from Carnegie Mellon and is currently a Senior Research Scientist at Mitsubishi Electric Research Labs.

Microsoft Distinguished Engineer, Brian Harry follows up on his recent announcement about Microsoft's acquisition of of devBiz, developers of TeamPlain Web Access for VSTS. Brian heads up our Visual Studio Team Foundation development team, based in Raleigh, NC. Note that TeamPlain is unrelated to Teamprise, which to quote Jim Newkirk, recently "announced a complimentary license of the Teamprise client suite for anyone wanting to connect to an open source project on CodePlex."

If you are an existing devBiz customer, I encourage you to think about and weigh in on the following comment, on Brian's weblog.

"Another set of feedback we've gotten revolves around the devBiz components products - devMail, devDns and others.  We have removed these products from the market and are unsure what our future plans for them are.  I've seen requests that we open source them among other things.  We are considering many options ranging from including them in other products to making the source available in some form - either to existing customers, publicly or otherwise.  We want to make sure that customers feel that they have a good path forward.  We hope to reach a conclusion on a plan in the next few weeks on this issue as well."

If the VSTS team decides to release some of the products Brian mentions as open source projects, I hope and wouldn't be surprised to see them posted on CodePlex, which runs on Visual Studio Team System.

With a farewell quote from the greatest American writer of all time, my friend, neighbor, and idea-mate, Alex Barnett has announced that he is leaving Microsoft and Redmond to join a startup in Utah: Bungee Labs. [Lump_in_throat]. If they had any idea of the potential that Microsoft is losing, with Alex's departure, Steve would be ranting, Bill would be knocking on Alex and Katia's door, this evening, and Mary Jo would be working overtime.

Alex who? Alex Barnett is one of the most brilliant "practitioners" of social software, on Earth. Alex lives in the future; he reads, blogs, and tags prolifically in the present; and he routinely conceives of BIG ideas that have or will soon change the way WE discover resources, connect, interact, and collaborate, on the World Wide Web. Alex is the only [other;-)] blogger whose RSS feed I have recommended to every member of my team, Microsoft.com Communities Technologies, and do to practically everyone else I work with with, inside and outside MSFT.

Although Alex and I didn't really connect until about a year ago (a fact which we both find odd given the proximity of our interests, jobs, and homes) Alex has fast become my singular idea mate. Recently, upon learning that I had yet to read The Singularity is Near, Alex purchased me a copy and delivered it to my doorstep. He's just that kind of guy.

Alex, you are a true friend and gentlemen. It has been my great, great honor to count you among my closest friends and colleagues. Whereas your physical presence, in Redmond will be missed, I'm sure we will remain close, by other means. Good luck and godspeed, in your future endeavors. If I start my own company, someday, you are hereby invited to be employee #3...#2 if my friend and mentor, Jonathan Gordon, turns down his offer.

Speaking of start ups...

If you, dear reader, are in the venture capital (VC) business and on the prowl for promising Web 2.0 assets (or Web 3.0, LOL) with a focus on platforms and tools, here are two, multi-million dollar tips that you would be an unwise to ignore:

1. Get in on the third round of Bungee Labs. History shows that one brilliant mind is the difference between bomb and bonanza and Alex is all o' that. For the record and in the spirit of full disclosure, I have no interests in or other ties to Bungee Labs...yet.
2. Subscribe to Alex's Blog (RSS). Corante did.

Recently, I attended the Microsoft Most Valued Professional (MVP) Attendee Party (thanks, Sean!) at the wonderful Boeing Museum of Flight, in Seattle, with my partner Dave Morehouse.

Our Mission
Find, gather requirements for, and validate our social software plans for what we stiltingly and half-jokingly refer to as "Microsoft.community" with a subset of our target customers: Chinese- and Japanese-speaking MVPs; our most likely early adopters in China and Japan. I invited and we were graciously accompanied by my college buddy, Jumi, who hails from Tokyo, as well as a colleague from China, who is the Program Manager on our extended team, at Microsoft's Advanced Technology Center, in Beijing.

Our Findings
One of the services we are planning to deploy (soon) as part of our integrated service offerings is a social bookmarking service, codenamed "Tagspace". Toward the end of the night, Jumi and I engaged in a colorful and informative conversation with three young Japanese MVPs, an exchange which later blossomed into a very hopeful theory.

Big in Japan
I xclaim that Japanese culture--a culture in which building concrete group consensus with as little conflict as possible is profoundly important--inclines the Japanese to embrace and value the product of Social Bookmarking (aka, Tagging) on the Web more completely and permanently more than any other culture. This is a UNTESTED theory.

The Follow Up
On Monday night, I floated my nascent theory over dinner to my friend Jumi, Alex Barnett, and our visiting colleague from China. Jumi surmised that it is more likely that social bookmarking will become an intense but short-lived fad than a permanent fixture of Japanese society/culture. I am well aware of that "Fads are an integral part of Japanese culture" (Parker, 1997). Fads, like every Japanese school child suddenly having to have a robotic dog, seem to wash over Japanese society each year like the coming and going of a great, memetic tide. Unsatisfied with Jumi's initial response, I pressed her to speculate on the possibility that social bookmarking might someday become as institutional and engrained in the Japanese psyche and "economy" as baseball or the Yen. Jumi demured. Alex, if you're reading this and assuming you've had a chance to give my theory some thought, what is your opinion?

What do you think?
If you are familiar with Japanese culture/society and social bookmarking (Joi Ito jumps to mind) or if you have information/research that would seem to affirm or contradict my theory that Tagging will be Big in Japan for longer than a typical Japanese fad cycle, please weigh in, by leaving a comment, below.

In the wake of a recent announcement by Redmond Mayor Rosemarie Ives that she will not seek another term of office, I was invited to and personally interviewed her two most viable successors: Councilman Jim Robinson and former councilwoman, Holly Plackett. I support both of these fine and experienced candidates in their mayoral campaigns, respect them immensely, value their views on community, and consider them both to be my friends and mentors. But don’t just take it from me! If you live in Redmond, the mayor's election is of great importance to you and most everyone you know. I strongly encourage you to research and get to know Jim and Holly yourself.*

         
     Jim Robinson                   Holly Plackett

After careful consideration and soul searching, I hereby announce my endorsement of Councilmember Jim Robinson to be the next chief executive and Mayor of the City of Redmond.

As a Planning Commissioner, it is my responsibility to represent the interests of the entire Redmond community: its current and future residents, employees, landowners, and business owners in the great little city of Redmond, WA by providing advice and channeling public feedback about current and long range Land Use Planning to Redmond's Mayor and City Council. Week in and week out for the past five years, I have studied, solicited and listened to public feedback about, and provided counsel on land use planning issues to Councilmember Jim Robinson and the other members of the City Council and Mayor Ives on questions such as:

• How many houses can be built on an acre and where, in the city?
• Should the City build out a Municipal Wi-Fi network?
• How wide must sidewalks be in the downtown area?
• Where should we have bicycle lanes?
• When, where, and how many native trees (and soil) can homebuilders remove?
• How much should existing residents pay for extra sewage capacity to accommodate new development, if any?

To provide informed answers to these and other questions, I make it my job to be well informed of the facts, issues, prevailing public opinion, and the personalities and positions of our elected representatives (like Jim Robinson, Kim Allen, and John Resha) and citizen advocates (like Holly Plackett), insofar as all of these inputs contribute, proportionally if not equally to the formation of sensible and progressive public policy. The Public comments. Commissioners listen and advise. Councilmembers enact. In this regard, I have interacted with, closely observed the statements and actions of, and have great respect for the integrity of and decision making abilities of both Jim Robinson and Holly Plackett.

Ms. Plackett has always impressed me with her boundless energy, expansive knowledge of even the most mundane aspects of public policy, her socially progressive views, and her optimistic, get it done attitude.

Mr. Robinson has impressed me with his patience, his open-minded approach to solving difficult problems, his tendency to reserve judgment until all the facts are in, and his passionate support of public pools, for the same reasons I support them: personal safety & education, lifetime health benefits, and recreation.

At the end of the day, Jim Robinson's skills, experience, qualifications, and connections, in combination, incline me to believe that he will make an excellent Mayor. For more information about both of these candidates, see:

Jim Robinson:

• http://www.robinsonformayor.com
• The Redmond Blog (by Bob Yoder)
• Seattle Times

Holly Plackett

• http://www.hollyplackett.com
• The Redmond Blog (by Bob Yoder)
• Seattle Times

*I also encourage you to contribute to their election campaigns, as I have done in equal amounts to ensure that we, the voters, are informed and educated about their qualifications and positions on the matters that count.

For my innaugural post of 2007*, I decided to wait for the Chinese New Year. Hey, why not? I have also decided to do something new: Randomize.

Occasionally, I send short "inspirational" videos to my teams in an often vain and frequently futile attempt to amuse, inspire, enliven, and inform their work on the mind-blowingly awesome sites and services that we are developing.

Last Week's Inspirational Video 2/14/2007
"Let's get on the hump, boys."
- Captain Kong, in Stanley Kubrick's immortal Dr. Strangelove.
click here to view the clip
 (get it? "hump"-tendre...)

My teams build social software for technical professionals. As such, we are blessed. We are also, sometimes, full of it. In advance of upcoming v1 releases, this Spring, I plan to "inspire" each of my sleep-deprived, stressed-out but nevertheless well-showered teammates, on at least a weekly basis. I've also decided to share my missives with you and the rest of the world.

Why randomize only ten world-class software developers and testers when I can randomize thousands of you?

This Week's Video Inspirational Video
"NO! This is COUNTER-dependency training…"
click here to view the clip
Date: 2/21/2007

If you work in the tech industry, my weekly video postings and my annotations thereto could give you a chuckle, summon a yawn, evoke an aha!, or convince you to eschew my blog, forever. But... If you take a step back, you might also get a pretty good sense of "where we are" in the development process and the prevailing mood of the team. Over time, I imagine that these videos/comments could, in combination, take on a life of their own and become an epic poem in which the informal histories of our software development projects are encoded, for posterity. Nahhhh.

*Where in the world has Korby Parnell been since December 2006? Short Answer: at my desk in Redmond mostly, making hay, hanging out with my lovely daughter, reading/tagging/reading, dreaming, getting back in touch with my customers' [_your_] pain, drawing up wireframes and breaking them down into scenarios and decomposing them into stories and disaggregating them into tasks and..., and refueling my blogine for 2007. How have you been? Well and happy, I hope!

My holiday dinner party went pretty well, by all accounts. Dinner was a little late in coming due to the amazing length of time required to bake a 5lb slab of sea bass at 350F. None of my guests seemed to mind, however. There were plenty of pupus and drinks. Conversation was pleasant. New connections and new friends were made. Wine flowed freely. Martinis were mixed and poured without ostentation in goblets: the closest thing I have to cocktail glasses.

The Bad and the Ugly

• My salad dressing was just wrong, due to a terrible decision to combine walnut oil with vegetable oil. Yuck.
• The sea bass was too tender. :-( It was like eating lobster. Next time, I'll use the broiler or barbeque.
• I inadvertently served out of date whipped cream (from a can, cringe) to 2 guests, with their cheesecake. I am so ashamed that I must apologize and atone, publicly, to assuage my guilt.
• Although the fried plaintain bananas (aka platanos fritos or tostones) were a crowd pleaser, 3-4 chips per plate, I didn't have enough hands to fry them up in the course of preparing my meal. I had to enlist the assistance of a dinner guest to finish the deed.

The Good

• An amazing group of amazing people. I will post links to photos here when my guests get around to uploading them.
• Desert: take a store bought cheesecake, ask your guests whether they prefer strawberry, marmelade, apricot, cherry, mango, passionfruit, or [some other fruit flavor that you have on hand]. Given their input, spread a thin layer of jam or jelly from your fridge over the top of your cheesecake. Democracy works!
• Blaukraut
• Saffron Cream Sauce

My non-traditional blaukraut and last minute saffron cream sauce garnered the most amount praise. Recipes below.

For the blaukraut (sweet, sour, and colorful)... braise 1/2 chopped red cabbage and 1/3 of a large, sectioned sweet onion in oil over medium high heat. Add 1/2 cup of chicken broth and reduce heat to medium (so that it stops hiss-boiling and bubbles contentedly). Add 1/4 cup of red wine vinegar and a small fistfull of brown sugar. Combine, sneak a taste when none of your dinner guests are looking to make sure it's not too sweet, reduce heat to low, add a few squirts of sherry, salt to taste, and simmer for ~30-45 minutes, stirring occasionally and adding more broth as necessary. The finished product should NOT, NOT, NOT be mushy. Serves 4-6. For my party, I doubled this recipe.

For the saffron cream sauce... In a separate cup, crumble 12 saffron strands and combine with 1/2 cup lukewarm water and 1/2 cup of chicken, fish, or vegetable broth. Let stand.

In a 12-14 inch saucepan, combine 2 tablespoons of clarified butter (available in tubs at your high end grocers) or olive oil, 1/2 cup of minced shallots or onion, and 2-3 finely, finely minced cloves of garlic. Heck, you might even mix in some minced leak stock for extra body, if you wanna get fancy.

When shallots are translucent, reduce heat to medium-medium low, throw in a few tablespoons of your saffron infused water and chicken broth, sprinkle all with a fine mist of sauce flour (finely milled) and combine thoroughly using a wire whisk or fork. Add a bit more broth and stir vigorously. Add another fine layer of flour. Combine until you see NO white whatsoever. Add another coating of flour and repeat the whisking. Repeat until you have achieved a viscosity that your meal demands of you and you have used up all of your saffron water/broth, adding extra chicken broth as necessary to build out the volume of your sauce. That done, add 3/4 cup of Half 'n Half or cream and reduce over low-low heat, stirring occasionally. If you time it right, which I did not quite do at my dinner party, your sauce will have returned to its desired viscosity, seemingly by magic, with the addition of no more sauce flour.

Just before serving the sauce, mix in 1 tablespoon of sherry and salt to taste. Optionally, you can add a sprinkle of cayenne powder. BE CAREFUL!!! Your saffron sauce should be delicate, above all else. As a rough rule, your cayenne should be noticeable to only the most sensitive palates. At my dinner party, it was noted by but one of my guests. Thanks Paige!

For the first time in a couple of years, I've decided to host a holiday dinner party for a few of my best friends, at my home in Redmond. For the sake of posterity and to give you some ideas for holiday meals you might want to prepare for your friends and family or request of that special cook in your life, here's what I plan to serve to my guests.

My Requirements: meal must be festive, semi-formal, multi-course, serve 14-16 people, and be as kosher as possible...if possible.

Pre-Dinner Cocktails
Unknown. I'll be asking my friends Phil and Alex: both 'maestros of mix' to prepare and serve up "festive" cocktails. Ho ho ho.

Starters (pupus)

• Cambazola, Mirabo, and plain brie on rosemary wafers with tropical fruit compote and/or fireweed honey. Plain croutons (sliced baguette fried golden brown with butter and light herbs and spices), a selection of harder cheeses, and kalamata olive tapanade, on the side.
• Pickle Tray: whole garlic cloves, jalepeno stuffed green olives, artichoke hearts, and pickled herring (a Svenska touch in honor of my heritage).
• Fruit Tray: fresh pineapple and a pomegranate garnished with fresh mint (yes, that's it)
• Bacon-wrapped jumbo prawns with a wedge of braised pineapple, because I figure we may well concentrate all that is unkosher in one side dish.
• Beverages: Hot, spiced apple cider AND/OR Pinot Noir, Cabernet Franc, Meritages, and other light reds from California's Napa Valley and Central Coast, Oregon's Willamette Valley, and Walla Walla, Washington. Chef juice.

Soup

• Roasted Carrot Soup--4oz, topped with a tablespoon-sized dollop of whole sour cream and a julienned spear of organic carrot, carmelized in clarified butter, with brown sugar, shallots, garlic, and sherry to al dente perfection (hopefully). Garnish, a sprig of fresh tarragon.
• Roasted Red Pepper and Tomato Bisque, upon request. Same portion size and toppings as the carrot soup. Garnish: fresh, minced chives.
• Beverages: Sparkling Water with a few drops of Pomegranate juice and AND/OR the remains of the reds, the cocktail dregs, or apple cider.

Salad

• Mixed Organic Greens topped with: crumbled gorgonzola, dried currants OR pomegranate seeds, and chopped walnuts. Accompanied by three, equally sized wedges of avocado, unpeeled mandarin orange, and Washington State pear.
• Dressing: approximately two parts raspberry dessert wine (framboise), one part balsamic vinegar, one part good old tap water, Salat-Kroenung Italienische to taste (Good Seasons Italian Dressing mix will do fine, in a pinch) and three-four parts walnut oil, the most important ingredient.
• Beverage: Ice water AND/OR a blend of TBD juices and water, probably inclusive of grapefruit, lime, and pomegranate (Thanks be to Trader Joe. You da man!)

Main Course

• 6 oz Chilean Sea Bass*: steamed, supple, and simple
• Substitute, upon request, of oven-roasted rosemary chicken breast (brined 2 hours), broiled filet mignon (rubbed with fresh minced garlic, coarse sea salt, and freshly ground pepper), broiled portabella mushroom, or eggplant korby-aise.
• Accompaniments:
• Sweet|Crunchy|Orange|Green|Vegetable: roasted, carmelized carrots and zucchini spears along with zucchini spears...and roasted red pepper if'n I'm inspired. (3-4oz)
• Crispy|Chewy|Salty|Yellow|Starch: platanos fritos(4-5, 1oz aka tostones)
• Sour|Red: blaukraut (2-3 oz)
• Sweet|Spicy|Brown: Chutney, made with love by my mom. (.5 ounce, served atop fish)
• Garnish: fresh, minced chives and fresh parsley sprigs
• Beverages: 2004 Silverado Cabernet Sauvingnon yumyumyum

Oooooh, I just realized that my meal is missing a "creamy" element. Hm, should I trade out the chutney for something else? Whatever it is, it must be slightly spicy.

Suggestions?

Dessert

• Cheesecake (4oz) with some kind of tropical fruit compote and fresh mint
• Beverages: coffee OR black tea, tawny port, and any other dessert wine that one of my guests brings.

*For the record, I only allow myself to prepare, serve, and eat Chilean Sea Bass once or twice per year. Guilty pleasure.