Return-Path: <stefano@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 82818 invoked from network); 3 Sep 2000 12:26:58 -0000
Received: from pop.systemy.it (194.20.140.28)
  by locus.apache.org with SMTP; 3 Sep 2000 12:26:58 -0000
Received: from apache.org (pv37-pri.systemy.it [194.21.255.37]) by
 pop.systemy.it (8.8.8/8.8.3) with ESMTP id OAA22105;
 Sun, 3 Sep 2000 14:26:44 +0200
Message-ID: <39B10CFA.1C587816@apache.org>
Date: Sat, 02 Sep 2000 16:21:46 +0200
From: Stefano Mazzocchi <stefano@apache.org>
Organization: Apache Software Foundation
X-Mailer: Mozilla 4.72 [en] (Windows NT 5.0; I)
X-Accept-Language: en,it
MIME-Version: 1.0
To: cocoon-dev@xml.apache.org
CC: ricardo@apache.org
Subject: Re: C2 XSP SQL taglib
References: <Pine.LNX.4.21.0009012147240.1802-100000@localhost.localdomain>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N

Donald Ball wrote:
> 
> On Fri, 1 Sep 2000, Ricardo Rocha wrote:
> 
> > We may also consider XSLT's own use of <xsl:element> where attribute
> > name can take a dynamic XPath expression:
> >
> >   <xsl:element name="{@tagname}">...</xsl:element>
> >
> > Since XSP doesn't support XSLT's {...} idiom inside attributes, we
> > may need to do something like:
> >
> >   <xsp:element namespace="http://localhost/foo">
> >     <xsp:name><xsp:expr>
> >       "new" + tagName
> >     </xsp:expr></xsp:name>
> >   </xsp:element>
> 
> fearfully, i point to a possibility inadequacy here. suppose, just
> suppose, the namespace weren't known at compile time either. should we
> make it complete by adding:
> 
>    <xsp:element>
>     <xsp:namespace>
>      <xsp:expr>unknownNamespaceString</xsp:expr>
>     </xsp:namespace>
>     <xsp:name><xsp:expr>
>        "new" + tagName
>      </xsp:expr></xsp:name>
>    </xsp:element>
> 
> i can assure you, i'll never actually _want_ to use this construct, but
> you _know_ someone will. right?
> 
> or we could bite the bullet and add {} expression processing to the
> attributes of certain xsp elements. that would cut down on the number of
> elements we need to add to the language.

Good point.

Ricardo, how hard would be to implement such an addiction?

-- 
Stefano Mazzocchi      One must still have chaos in oneself to be
                          able to give birth to a dancing star.
<stefano@apache.org>                             Friedrich Nietzsche
--------------------------------------------------------------------
 Missed us in Orlando? Make it up with ApacheCON Europe in London!
------------------------- http://ApacheCon.Com ---------------------