Knowledge Architect/Operation/Sharing

Sharing

Clearly, knowledge has no value if it is not (expressed and) shared in some way.

Also clearly, by definition, freely available knowledge has no market value of its own, as at best, some agents like search engines can associate advertising to the search process on “free” information and manage to derive a market value, but that value is not the value of the free content, but the value of the advertising valued search service.

Knowledge (and information) value is defined by the associated entitlement, and the implementation thereof.

Of course, offer and demand are also applicable factor, when knowledge and information have an effective value, and where entitlement is the differentiating factor between sharing and giving.

More so, with inadequate entitlement support, much knowledge is not shared, even when sharing it, for example, would enable collaboration, the greatest productivity tool. Not only without entitlement, knowledge has no market value, but the lack of entitlement support deprives all, of major productivity gains, incurring the associated value loss and costs.

Collaboration, the most effective productivity tool, is founded and based on knowledge and knowledge resource sharing, yet it is drastically hindered without entitlement.

Yet, entitlement (See Entitlement above) cannot be effectively implemented without adequate knowledge architecture and an associated resource entitlement, modeling, management, and sharing (REMMS) environment to manage it.

There are many requirements to effective knowledge and resource sharing, including all communication, language, and notation aspects, as well as access control issues including authentication, authorization, classification cryptography, duplication, privacy, and related considerations.

Still that is not all as publishing and distribution also introduce crucial sharing considerations.

As this document can only briefly note some knowledge sharing issues, and as some communication, language, and notation aspects have already been noted when considering knowledge resource modeling, this section briefly considers some access control and publishing related aspects.