SnipSnap right now is more a KM framework than really a tool. But with Labels you can express a lot of things, for examples skills (type:person) or requirements (type:requirement) together with an ontology (category:Java,XML). And this would work for enterprise KM I guess. You would have to define finer grained privelages and macro plugins, but yes then I think it would be usable.CMS and Weblogs are only a small part of what we have in mind. CMS (Wiki) and weblogs are to incarnations of SnipSnap as KM software. Perhaps you'll search the web for k-logs (Knowledge-Weblogs).There will be support for Requirement Engineering, Knowledge rating and Datamining in future release of SnipSnap (perhaps SnipSnap XL).And my credo is: People use simple tools.
@pmode: Its not clearly defined what an enterprise KM must look like, but I think, the representation of SnipSnap as a WikiWeb is not easy enough to use for people. I am not thinking of enterprises related to IT or the internet, but enterprises with less IT-educated workers, e.g. insurances.
Those people might be frightened by a pure "text-based" system, where you have to learn a special syntax !?@funzel: I believe, there could be possibilities for using the technology to link all content, users, and the labels you talk about. but I think more metadata is needed to implement a more powerful search engine.
@tengri: what metadata do you need ? With typed links and Labels you can add all metadata you need. Search engine:
Lucene can search for fields with "field:name" so you could search for all Snips with label "Type:requirement" and "Project:KOGITO" with "type:requirement AND project:KOGITO"
We're looking into TQL as a tree query language with prolog like features.
What is SnipSnap?
SnipSnap is a free and easy to install weblog and wiki tool written in Java.
Current version: 1.0b3-uttoxeter Try our Web Start Demo!Resources
I'll fix that.Fixed.