Collective Intelligence

Imagination is more important than knowledge
— Albert Einstein

I believe this more than ever. Blogs are a good example. I enjoy reading blogs. In them, you get a glimpse into the imaginative mind of the blogger. Because I am a bit of a techie, Jon Udell is one of my favorites. I personally think he is an idea machine.

Talking about idea machines, I am privileged to spend some time with Doug. I met him almost a year ago and it is one of the most transforming events in my life. He is the closest to a real genius I ever met. His thinking is refreshingly different.

He is well known as the inventor of the mouse. There are lot of other ideas of his that do not get as much attention. I plan to blog a bit about some of these in the coming weeks. If you have not done so, it is worth reading a few of his papers.

I will close with a few things to ponder about.

What is Collective IQ?
How do you Augment Human Intellect?
What is a Networked Improvement Community?
How do you build a Dynamic Knowledge Repository?


XDocs and the age of new XStars ( X* ?)

Last week Microsoft executive started talking about XDocs. Here is Microsoft’s description. “XDocs,” a code name for the newest member of the Microsoft Office family, streamlines the process of gathering information by enabling teams and organizations to easily create and work with rich, dynamic forms. . A few usage scenarios on this page talk about some sample applications.

Here is my wishlist for XDocs or similar technology.

XDocs web component ( an .net component, activex control, java applet or some similar web object). This will allow me to insert an XDoc anywhere in a webpage. This means, all the website interactions with the visitors will be based on custom schemas and will have better semantics.

XDocs Office Component. Imagine the ability to click on File/New in Microsoft Word and see a bunch of XDoc style sheets. When I pick one, it looks like a Word document with sections. For example, as a marketing dude, I choose a document called Customer Visit. This document contains sections where I can type customer contact information, feature requests, reactions to prototypes I presented etc. Once I enter this document, different parts of the documents are streamed as XML to different applications. For example, the feature requests may be automatically inserted in a product database.

XDocs mail component. Somewhat similar to the scenario above, except that when I Compose/Create a new mail, I get to pick one of the pre-defined formats (each one based on an XDocs format). Let us say that it is a simple meeting request. When I send it out, it goes to my colleague. When my colleague opens the mail he is prompted to Accept/Reject/Request Postponement. The last option appears only if he has a conflict in his calendar (magically performed by an plug-in in the email client which can process XML). I know that this stuff works in outlook. But I would like it work in yahoo, hotmail or any other mail system or webmail client. When my colleague clicks Accept, his calendar is updated automatically. A development kit to allow me to define my own sequence of actions for each type of mail I receive would make it even more extensible.

Let us assume that have a new collaborative environment called XGroups based on XDocs as the underlying format. It has the ability to create your own message types. If I want to compose a plain old message, I simply pick normal as the type and I get the conventional email style message. But think of what can happen in this group. This is an extensible infrastructure. Let us decide that our XGroups decide to share a bunch of bookmarks. We simply design an XDoc called Bookmark. When I compose a message, I pick Bookmark style and simply enter a web page address. As a product team, we may decide to have message type called Feature Request. Everytime someone enters a feature request, it looks a like a normal message but is automatically tagged with the product name, the source of the request (customer, internal etc) and the request text. As we interact using XGroups, we are building a knowledge base behind the scenes.

What will have next? XMail (XML based email), XMTP ( like SMTP except it is structured with XML messages), XTTP ( like HTTP but will get/send xml streams for apps). With all this we may really need an XVM (an XML virtual machine).

XMLization of the Web

XMLization of the web is bound to happen sooner are later. Already several websites deliver content in XML format. One of the popular XML tool vendors Altova of XMLSpy fame, announced Stylevision(TM) for building XML websites and converting HTML websites to XML. In my opinion, XMLization of the web is the first step towards moving to the Semantic Web.

When content travels from a backend database to the web page, somewhere along the line the semantics are lost. This problem can be avoided by keeping the web content in XML. Also, you get a host of other advantages like the easy repurposing of content, ability to exchange rich data with other applications, etc. This ability just gets us to the first step of an immensely interoperable web.

IDC predicts that the XML tools development market will reach $395 million by 2006 at a compound annual growth rate (CAGR) of 41%. While most of the web publishing is about content, increasingly websites will merge content with applications. This movement opens up entirely new opportunities for XML components. It will be interesting watch evolution in this space.

Update – May 2016

It did happen (XML as the content format for web) and was dropped for html5. There are several reasons for this shift. XML, however, continues strong and appears in places you don’t expect (for example, as the definition of UX).