Return-Path: 
 <cocoon-dev-return-19540-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 90980 invoked by uid 500); 5 Dec 2001 20:33:41 -0000
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:cocoon-dev-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-dev-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-dev@xml.apache.org>
Reply-To: cocoon-dev@xml.apache.org
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 90967 invoked from network); 5 Dec 2001 20:33:40 -0000
From: "Steven Noels" <stevenn@outerthought.org>
To: <cocoon-dev@xml.apache.org>
Subject: RE: [Summary] Dreams, RTs and getting the stuff done
Date: Wed, 5 Dec 2001 21:33:44 +0100
Message-ID: <OKEDLKGMIPDOCJHOEDEFKEHHCHAA.stevenn@outerthought.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
In-Reply-To: <3C0E7268.8CC3BC52@apache.org>
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

> -----Original Message-----
> From: Stefano Mazzocchi [mailto:stefano@apache.org]
> Sent: woensdag 5 december 2001 20:16
> To: Apache Cocoon
> Subject: [Summary] Dreams, RTs and getting the stuff done
>
>
> I've been having a private conversation from somebody on the list that
> 'suggested' that we should focus on something and getting it done rather
> than dreaming on many things and dilute our effort.

here's 'somebody' - perhaps we should mention that it started off with severe mutual
misunderstandings & subsequent impoliteness ;-)

> 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.
>
> The map between those pieces and existing software is *far* from being
> accomplished but we are heading in the right direction.

To conclude our private conversation: a KMS should *at least* be able to facilitate &
support the cycle you mention above:

  +->  research ----> develop ---> produce ----> use --+
  |                                                    |
  +---------------------- report ----------------------+

and as such is likely to have some overlaps with the d-haven.org/docoport dream
mentioned earlier on this list. KM in my perspective is something which can be
supported by such technology, but is not a technology by its own.

By massaging & managing the many carefully crafted but sometimes hard to digest RT's
into such KM-supporting technology, more people will be able to collaborate better on
big, beautiful but complicated projects such as cocoon.

Jummy... fun times ahead!

</Steven>


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org