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 60088 invoked from network); 8 Feb 2001 14:56:44 -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 14:56:44 -0000
Received: (qmail 24579 invoked from network); 8 Feb 2001 14:55:53 -0000
Received: from unknown (HELO lap1) (giacomo@192.168.222.104)
  by limbo.otego.com with SMTP; 8 Feb 2001 14:55:53 -0000
From: Giacomo Pati <giacomo@apache.org>
Organization: Apache Software Foundation
Date: Thu, 8 Feb 2001 15:55:54 +0100
X-Mailer: KMail [version 1.1.99]
Content-Type: text/plain;
  charset="us-ascii"
To: cocoon-dev@xml.apache.org
References: <3A81AC3D.E2B77108@apache.org>
In-Reply-To: <3A81AC3D.E2B77108@apache.org>
Subject: Re: Standardizing XSP Namespaces
MIME-Version: 1.0
Message-Id: <01020815555408.01059@lap1>
Content-Transfer-Encoding: quoted-printable
X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N

Berin Loritsch wrote:

<snip/>

> sendmail | http://apache.org/cocoon/sendmail/v1    | sendmail     | htt=
p://apache.org/cocoon/sendmail/v1
> esql     | http://apache.org/cocoon/SQL/v2         | esql         | htt=
p://apache.org/cocoon/SQL/v2
>
> This is before I start porting the rest of the core
> Logicsheets to Cocoon 2.
>
> Cocoon 2 URIs
> -------------------
> pros: simple, short
> cons: no versioning
>
> Cocoon 2 URIs
> -------------------
> pros: versioning
> cons: long
>
> My proposal is to make all the URIs like the last two entries
> (sendmail and esql), because they are simple, and versioning
> is included.

+1=20
IIRC we (C2) decided many month ago to shorten the uri to apache.org=20
without the www because it doesn make any sense. Unfortunately we missed
to define versioning.

> Also--until dependence on the prefix are resolved we should
> standardize on the Cocoon 1 prefixes.
>
> After dependancies on prefixes are resolved, the expected
> results should be that if the stylesheet creates elements,
> they should belong to the associated namespace, using the
> default prefix.
>
> That means that <request:get-parameter name=3D"foo" as=3D"xml"/>
> will _always_ return <request:parameter>bar</request:parameter>
> even if the parameter was retrieved with
> <xsp-request:get-parameter name=3D"foo" as=3D"xml"/>

+1 as well. Seems to be a good standard

Giacomo