> From: Stefano Mazzocchi <[EMAIL PROTECTED]> > Reply-To: [EMAIL PROTECTED] > Date: Wed, 05 Dec 2001 20:15:52 +0100 > To: Apache Cocoon <[EMAIL PROTECTED]> > Subject: [Summary] Dreams, RTs and getting the stuff done > > > > Stream of Thought #2: The perfect KMS > ------------------------------------- > > KMS stands for "knowledge management system". It's a marketing buzzword > that indicates systems (mostly targetted for intranet use) that are > capable of managing and making available 'corporate knowledge', the > company information, in such a way that it's easily created, easily > published and easily accessible. > > A typical KMS is composed of: > > 1) a front-end > 2) a back-end > 3) a content-editing system > 4) a search engine > 5) an administration toolkit > > the idea is to come up with solid and open software solutions that > implement all the above key pieces, then sell the service to glue them > together for customer needs.
Another use for this system is a Course Management System. I would love to have an Open Source Solution that is already going where most of the major commercial CMS vendors are going. > > The map between those pieces and existing software is *far* from being > accomplished but we are heading in the right direction. My guesses are > for software mapping are: > > 1) front-end -> Cocoon > 2) back-end -> XIndice or a Cocoon-based CMS layer wrapping XIndice > 3) editing system -> ??? (Mozilla based inline editor being my best > guess) > 4) search-engine -> ??? (The lucene-based indexing appears a first step > in the right direction) 4.1 a user/data management layer where we can record and archive information about the users' interaction with the system. Perhaps as simple as a database that gets created for each instance. > 5) administration toolkit -> cocoon webapp > > I will now explain my ideas on each component. > > - o - > <section sniped> > Stream of Thought #2.3: The content-editing system > -------------------------------------------------- > > Following the SoC patterns, content should be edited and modified by > editors, people that have specific writing and authoring skills but > normally lack technical ones. > > For this reason, the editing system should require the little possible > effort and integrate seemlessly with the editing environment the persons > are used to. > > At the same time, the software should not give any more editing freedom > than what their concerns require. For this reason, a pure WYSIWYG > solution is considered harmful. > > The proposed solution is a constrained-WYSIWYG editing system that > allows visual feedback to help the writer contextualize the edited > content, thus simplifying the editing approach, but limits the editing > capability to those areas where writer is allowed/capable of working on. You lost me here. You're presuming that whoever works with this editor already has a skill set of, at least, HTML, correct? I would love to see the results and help as much as I can, although I'm a very beginner Java programmer, I've always loved Cocoon as a concept and as an application Carlos -- Carlos E. Araya ---+ WebCT Administrator/Trainer G | California Virtual Campus - | C/O De Anza College P | 21250 Stevens Creek Blvd ---+ Cupertino, CA 95014 email [EMAIL PROTECTED] web http://www.cvc1.org/ (work) http://www.silverwolf-net.net (personal) phone 408 257 0420 (work) PGP Fingerprint E629 5DFD 7EAE 4995 E9D7 3D2F 5A9F 0CE7 DFE7 1756 Choose your friends by their character and your socks by their color. Choosing your socks by their character makes no sense, and choosing your friends by their color is unthinkable." --anonymous --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
