Knowledge management is more than just contributing, discovering and consuming content. Not only do I have to be able to store the right stuff, find the right stuff and learn from the right stuff, but what I am and am not authorized to see has to be managed. A platform like TechLore has to be intelligent enough to make sure that the right people see content and the wrong people don't. It's two halves of the same whole.
So, here's the vision... Imagine this platform as the solution to my company's knowledge management needs. Let's say my company is Widgets-R-Us, the leading maker of widgets in the fantasy of my own mind. Here at WRU, we know alot about widgets that we need to store and manage so that it can be effectively shared with the various makers and movers and shakers in our company. This is internal information. The TechLore platform can help with that. But it can't help me restrict that information from the outside world; instead I rely on things like my network topology to do that.
We (at WRU) don't want everyone on earth to know what we know about widgets ... or it's closin' time, baby! However, there's alot of knowledge we *would* like to share with customers, and even more we'd like to share with partners. Why can't the platform help me with that?! Why should I store knowledge in more than one place? Why is my public FAQ written in HTML, while my customer-facing knowledge base and internal KMS are totally disparate systems containing lots of duplicate data?
Instead, I have a dream of a TechLore that holds ALL that information. Isn't that what various skins are for? And when I contribute, I could authorize discovery and consumption. Now, my picture of knowledge management is one (giant) step closer to completion.
What do you say, Capable Networks? Interested?
