Return-Path: 
 <cocoon-dev-return-30130-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 28161 invoked by uid 500); 6 Aug 2002 12:20:08 -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 28150 invoked from network); 6 Aug 2002 12:20:08 -0000
Date: Tue, 6 Aug 2002 08:20:08 -0400
Subject: Re: [CLEANCOON] Let's clean Cocoon and modularize it  (was: Cocoon
 Organization (Cocoon plugins))
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v482)
From: Jason Foster <jafoster@uwaterloo.ca>
To: cocoon-dev@xml.apache.org
Content-Transfer-Encoding: 7bit
In-Reply-To: <NCBBKFMJCLIMOBIGKFMJMEKLHPAA.ldodds@ingenta.com>
Message-Id: <D88E2708-A936-11D6-82F0-000A27E14D02@uwaterloo.ca>
X-Mailer: Apple Mail (2.482)
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

<snip/>

With respect to choosing a Wiki, I think that we should (to use a Steve 
Jobs euphemism) "eat our own dogfood" and either use the existing WikiLand 
or...

> As an aside, something else worth looking at is WikiML:
>
> http://www.wikiml.org
>
> It's a SAX parser for reading Wiki markup and spitting out XHTML.
> It'd be very simple to repackage it as a Cocoon Generator, and
> generalise the markup it creates.

Given that Cocoon is supposed to be a whiz-bang framework, it would be 
pretty weird, if not disconcerting to people looking at adopting the 
framework, not to use it ourselves.

Jason Foster


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