Return-Path: 
 <cocoon-dev-return-40949-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 30088 invoked by uid 500); 29 Apr 2003 08:03:24 -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 30073 invoked from network); 29 Apr 2003 08:03:23 -0000
Received: from office.oilspace.com (213.219.58.70)
  by daedalus.apache.org with SMTP; 29 Apr 2003 08:03:23 -0000
Received: from kpiroumian (ns.informtek.com.ru [195.239.59.130])
	by office.oilspace.com (Postfix) with SMTP id F1E5818A
	for <cocoon-dev@xml.apache.org>; Tue, 29 Apr 2003 09:03:33 +0100 (BST)
Message-ID: <00b801c30e25$db64c8e0$a52efea9@kpiroumian>
From: "Konstantin Piroumian" <kpiroumian@apache.org>
To: <cocoon-dev@xml.apache.org>
References: <3EADB041.4090003@apache.org>
Subject: Re: Semantic analysis of the namespace URI used in Cocoon HEAD
Date: Tue, 29 Apr 2003 12:03:43 +0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

From: "Stefano Mazzocchi" <stefano@apache.org>

> In light of contrast solidity, I armed myself with grep and patience and
> went thru the entire CVS HEAD to find out all the cocoon-related
> namespace URIs that we use.
> 

<skip what="namespace summary"/>

> 
> Final thoughts
> ==============
> 
> I'm perfectly aware that all those changes are back-incompatible, but,
> IMO, we *MUST* make an effort to keep a registry of the namespaces used
> and make sure we both control them and keep an eye on their pattern
> coherence.
> 
> I also propose that *everytime* code is added in CVS that introduces or
> works on a new namespace, a vote has to take place on the URI used for
> that namespace.

+1 for all.

Regards, 
  Konstantin

> 
> 
> 
> Thoughts?
> 
> 
> -- 
> Stefano.
> 
> 
> 
>