Return-Path: <balld@webslingerZ.com>
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 82266 invoked from network); 2 Sep 2000 01:48:39 -0000
Received: from balld-0.dsl.speakeasy.net (HELO localhost.localdomain)
 (@216.254.77.75)
  by locus.apache.org with SMTP; 2 Sep 2000 01:48:39 -0000
Received: by localhost.localdomain (Postfix, from userid 501)
	id E11A7480F; Fri,  1 Sep 2000 21:51:21 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1])
	by localhost.localdomain (Postfix) with ESMTP
	id DE9056087; Fri,  1 Sep 2000 21:51:21 -0400 (EDT)
Date: Fri, 1 Sep 2000 21:51:21 -0400 (EDT)
From: Donald Ball <balld@webslingerZ.com>
X-Sender: balld@localhost.localdomain
To: cocoon-dev@xml.apache.org, ricardo@apache.org
Subject: Re: C2 XSP SQL taglib
In-Reply-To: <39B040F5.B679836E@apache.org>
Message-ID: <Pine.LNX.4.21.0009012147240.1802-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N

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.

- donald