Return-Path: <giacomo@apache.org>
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 63461 invoked from network); 8 Feb 2001 15:05:14 -0000
Received: from otego-gw-1.dataway.ch (HELO limbo.otego.com) (195.216.80.13)
  by h31.sny.collab.net with SMTP; 8 Feb 2001 15:05:14 -0000
Received: (qmail 24607 invoked from network); 8 Feb 2001 15:05:11 -0000
Received: from unknown (HELO lap1) (giacomo@192.168.222.104)
  by limbo.otego.com with SMTP; 8 Feb 2001 15:05:11 -0000
From: Giacomo Pati <giacomo@apache.org>
Organization: Apache Software Foundation
Date: Thu, 8 Feb 2001 16:05:11 +0100
X-Mailer: KMail [version 1.1.99]
Content-Type: text/plain;
  charset="us-ascii"
To: cocoon-dev@xml.apache.org
References: <Pine.LNX.4.21.0102081051360.2988-100000@jack.sergeant.org>
 <3A82A2F0.A81D3D51@apache.org>
In-Reply-To: <3A82A2F0.A81D3D51@apache.org>
Subject: Re: Standardizing XSP Namespaces
MIME-Version: 1.0
Message-Id: <0102081605110A.01059@lap1>
Content-Transfer-Encoding: quoted-printable
X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N

Berin Loritsch wrote:
> Matt Sergeant wrote:
> > On Wed, 7 Feb 2001, Donald Ball wrote:
> > > i'd almost concur, but on the xsp-dev list, matt requested a move t=
o a
> > > cocoon-agnostic namespace for shared xsp logicsheets (he has an imp=
l of
> > > esql and is discussing doing some others). on the one hand, he's go=
t a
> > > point, maybe something like this would be better:
> > >
> > > http://apache.org/xsp/sendmail/v1
> > >
> > > on the other hand, i'd hate to make people change namespaces again.
> > > boy, it sure seems like the namespace working group could have
> > > antipicated this problem and written in some support for namespace
> > > migration... well, c'e la vie. anyway, i have no strong opinion one=
 way
> > > or the other, so i'd let people vote. do we stick with this scheme
> > >
> > > http://apache.org/cocoon/sendmail/v1
> > >
> > > or generalize to
> > >
> > > http://apache.org/xsp/sendmail/v1
> >
> > I agree that switching namespaces is a pain. Can we decide that its
> > policy for Cocoon to put future taglibs in the /xsp/ rather than /coc=
oon/
> > namespace?
>
> +1 Totally.  That is the whole point of this proposal.  Identify the
> standard namespace URI structure for all Cocoon taglibs.
> That makes the handling of all taglibs the same.  It also makes it easi=
er
> to place them in one shared location so that we are only maintaining on=
e
> set of taglibs.

Well, I'd like to switch to the /xsp/ namespace completely for C2. I thin=
k we=20
are in the position to do it still right before any release of C2.

Giacomo