I see your point about reinforcing the notion of using a namespace for each taglib.  However, we have elements in our XSP page that are associated with a namespace that is not associated with any taglib. This forces us to declare that namespace in a child of <xsp:page>.  It makes it awkward for those who use namespaces in their system for other purposes since it adds more meaning to the simple declaration of a namespace.

For example, in C1 we have to declare the wdk namespace in the wdk:page element, but it is customary to define them all at the document root which is xsp:page:

<xsp:page language="java" xmlns:xsp="http://www.apache.org/1999/XSP/Core" xmlns:wdktags="http://www.saba.com/XML/WDK/taglib">

  <wdk:page xmlns:wdk="http://www.saba.com/XML/WDK">
    <wdk:head>
        ...
    </wdk:head>
    ...
    <wdk:widgets>
        ...
    </wdk:widgets>
  </xsp:page>
</xsp:page>
 
-----Original Message-----
From: Ricardo Rocha [mailto:ricardo@apache.org]
Sent: Tuesday, December 05, 2000 6:49 AM
To: Cocoon Developers
Subject: Re: taglibs (was: XObject)


Torsten Curdt wrote:

>> The current XSP implementation allows for the inclusion of
>> "not-builtin" libraries by means of _top-level_ <xsp:logicsheet>
>> directives or root-level <?xml-logicsheet?> pi's.
>
> Some more questions:
>
> Which syntax should be preferred <xsp:logicsheet> or the PI?