Social Glass

The semantic web is often heralded as the next evolution of the internet, Web 3.0. Wikipedia describes the semantic web as an:

evolving extension of the World Wide Web in which web content can be expressed not only in natural language, but also in a format that can be read and used by software agents, thus permitting them to find, share and integrate information more easily.

Indeed the semantic web promises to make entities like “address”, “contact info.”, etc. which appear within unstructured text on web pages, to be machine parsable through the use of microformats. Other semantic web standards, such as OWL, aim to define the relationships between objects and attributes within a pre-determined ontology.

Behind the firewall, an intranet marked up according to these standards would be information Garden of Eden with relationships between knowledge and metadata about content items being deeply embedded. The Discovery process on such an intranet would certainly be very rewarding given this abundance of “information about information”.

All of this works if content is published using the structural components the semantic web requires. And herein lies the problem - structure.

Within the context of Enterprise 2.0 we often talk about wikis and blogs being emergent - meaning they adapt to the needs and requirements of the knowledge worker. We want knowledge workers to impose their own structures, perhaps with minimal guidance through the use of patterns like scaffolding.

So how are we going to enforce the use of, say, microformats every time a knowledge worker writes an address or somebody’s contact information? Personally, I can’t think of a way without imposing structure. And I’d hate to see said structure reduce participation.

I believe in the value proposition of the semantic web, but to maintain current emergence capabilities, wiki and blog technology will have to be significantly enhanced to automatically mark up content when published. I think we’re a long way off from that being possible.