Return-Path: 
 <dev-return-44518-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org>
Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org
Received: (qmail 40260 invoked by uid 500); 6 Jul 2003 12:04:02 -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 40245 invoked from network); 6 Jul 2003 12:04:01 -0000
Received: from smtp8.wanadoo.fr (HELO mwinf0102.wanadoo.fr) (193.252.22.30)
  by daedalus.apache.org with SMTP; 6 Jul 2003 12:04:01 -0000
Received: from anyware-tech.com (AToulouse-206-1-7-141.w81-50.abo.wanadoo.fr
 [81.50.197.141])
	by mwinf0102.wanadoo.fr (SMTP Server) with ESMTP id 8FAE51BFFFA4
	for <dev@cocoon.apache.org>; Sun,  6 Jul 2003 14:04:01 +0200 (CEST)
Message-ID: <3F081033.6000500@anyware-tech.com>
Date: Sun, 06 Jul 2003 14:04:03 +0200
From: Sylvain Wallez <sylvain.wallez@anyware-tech.com>
Organization: Anyware Technologies
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.3) Gecko/20030312
X-Accept-Language: fr, en-us, en
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: Allow non-Cocoon elements in sitemap?
References: <20030706071509.GG672@expresso.localdomain>
In-Reply-To: <20030706071509.GG672@expresso.localdomain>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Jeff Turner wrote:

>Hi,
>
>Currently, if the treeprocessor encounters any nodes outside the
>'http://apache.org/cocoon/sitemap/1.0' namespace, it throws an exception.
>
>I would like to modify this behaviour to simply ignore non-Cocoon
>elements.
>
>
>My use-case is that in Forrest, I'd like to document our numerous
>sitemaps with some embedded XML:
>
><map:sitemap xmlns:map="http://apache.org/cocoon/sitemap/1.0"
>             xmlns:doc="http://apache.org/forrest/documentation/1.0">
>  
>
<snip/>

>Anyone mind if I make this (one-line) change?
>  
>

Although this sounds good, what about sitemap validation ? Can we tell 
RNG to ignore foreign namespaces ? Also, I envision some problems if we 
use these foreign namespaces in the <map:components> section, which is 
the xconf of a ComponentManager.

A possible solution is to filter any element or attribute having a 
namespace different than "" or the sitemap namespace from what is used 
by the TreeProcessor to build the sitemap. But this prevents components 
using namespaced configurations (AFAIK we haven't any as of today).

Or we could also filter the opposite way : configure the TreeProcessor 
with a list of allowed foreign namespaces that are ignored, any other 
namespace being considered as an error.

Sylvain

-- 
Sylvain Wallez                                  Anyware Technologies
http://www.apache.org/~sylvain           http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }
Orixo, the opensource XML business alliance  -  http://www.orixo.com