Return-Path: 
 <dev-return-63920-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org>
Delivered-To: apmail-cocoon-dev-archive@www.apache.org
Received: (qmail 74512 invoked from network); 30 Jul 2004 18:46:51 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur-2.apache.org with SMTP; 30 Jul 2004 18:46:51 -0000
Received: (qmail 87715 invoked by uid 500); 30 Jul 2004 18:46:46 -0000
Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org
Received: (qmail 87545 invoked by uid 500); 30 Jul 2004 18:46:44 -0000
Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:dev-help@cocoon.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@cocoon.apache.org>
list-post: <mailto:dev@cocoon.apache.org>
Reply-To: dev@cocoon.apache.org
Delivered-To: mailing list dev@cocoon.apache.org
Received: (qmail 87529 invoked by uid 99); 30 Jul 2004 18:46:44 -0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=FORGED_RCVD_HELO
X-Spam-Check-By: apache.org
Received: from [195.130.132.44] (HELO poros.telenet-ops.be) (195.130.132.44)
  by apache.org (qpsmtpd/0.27.1) with ESMTP; Fri, 30 Jul 2004 11:46:42 -0700
Received: from localhost (localhost.localdomain [127.0.0.1])
	by poros.telenet-ops.be (Postfix) with SMTP id 7BD123BC0F8
	for <dev@cocoon.apache.org>; Fri, 30 Jul 2004 20:46:36 +0200 (MEST)
Received: from gabriel.local (D5E009B7.kabel.telenet.be [213.224.9.183])
	by poros.telenet-ops.be (Postfix) with ESMTP id 448BB3BC059
	for <dev@cocoon.apache.org>; Fri, 30 Jul 2004 20:46:36 +0200 (MEST)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by gabriel.local (Postfix) with ESMTP id 78C9B42F05A
	for <dev@cocoon.apache.org>; Fri, 30 Jul 2004 20:46:38 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v618)
In-Reply-To: <410A1DDE.7030506@lineone.net>
References: <C726734B5ACA2445B2BB93E87ADD50331DB3D3@akxch03.tvnzad.tvnz.co.nz>
 <4106D407.9070209@umn.edu> <4107093D.3000802@reverycodes.com>
 <CF61BD94-E069-11D8-A4E0-000A95DC4186@apache.org>
 <41076488.6060307@s-und-n.de> <410767CB.1060308@mobilebox.pl>
 <410771AD.2080507@s-und-n.de> <4107EE77.6060600@apache.org>
 <410850BE.0@pcextremist.com> <410A1DDE.7030506@lineone.net>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <C9E8D49A-E258-11D8-9779-000A958B684A@outerthought.org>
Content-Transfer-Encoding: 7bit
From: Steven Noels <stevenn@outerthought.org>
Subject: Re: [RT] A Groovy Kind of Sitemap
Date: Fri, 30 Jul 2004 20:46:37 +0200
To: dev@cocoon.apache.org
X-Mailer: Apple Mail (2.618)
X-Virus-Checked: Checked
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

On 30 Jul 2004, at 12:07, Vilya Harvey wrote:

> A scripting language feels like overkill for simple pipelines, but the 
> XML syntax is very awkward for more complicated ones. The appropriate 
> choice comes down to how soon you feel that cutoff occurs, for the 
> kind of sites you develop.

If the complexity of a sitemap becomes too troublesome to express using 
XML, I'm pretty sure adding yet another concern to the same artefact 
won't help - quite the contrary. I'm pretty sure some sitemaps "out 
there" are simply too complex because people use all sorts of twisted 
pipeline constructs and components, just to avoid writing some lines of 
flowscript or an Apple, or use Java proper. What some people feel like 
a disadvantage (splitting flow and pipelines into separate artefacts), 
I feel like a distinct advantage of Cocoon. With my peanut brains, I'm 
able to understand more advanced Cocoon apps when I see a <map:call 
function|continue> and some internal-only pipelines which are called by 
flow functions with a well described Map of input parameters. This is 
all highly personal, of course.

</Steven>
-- 
Steven Noels                            http://outerthought.org/
Outerthought - Open Source Java & XML            An Orixo Member
Read my weblog at            http://blogs.cocoondev.org/stevenn/
stevenn at outerthought.org                stevenn at apache.org