cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefano Mazzocchi <>
Subject Re: [PATCH] Sitemap Draft - Misc. fixes and preliminary schema
Date Mon, 03 Jul 2000 21:26:59 GMT
"N. Sean Timm" wrote:
> "Niclas Hedhman" <> wrote:
> > > I've included a diff inline for some changes to the sitemap draft
> document.
> > > One of the changes involved declaring namespaces for all of the
> parameters
> > > for each component.  This was rather annoying (to me), and I think I'd
> > > personally rather see something along the lines of <param name="foo"
> > > value="bar"/>, but maybe there is a good reason for why it is the way it
> is.
> >
> > The <serializeparams> and <svgparams>
> > -1.
> > The map: namespace for the attributes (I believe) is for making the
> equivalence
> > between;
> >
> > <doc-type map:value="bac.dtd" />
> > and
> > <doc-type>bac.dtd</doc-type>
> But any custom transformer or serializer you write that isn't part of the
> base Cocoon distribution won't be a part of the map namespace.  Why should
> the ones that come with Cocoon be any different?

I totally agree, this is why they didn't have any namespaces specified.

> I don't like the idea that
> those parameters can reside in the map namespace while others have to be
> separate.  It just doesn't seem right...anyway, with the examples in the
> sitemap draft, they weren't in the map namespace (the values were, but not
> the parameter name).

The values are different, because this is a special attribute that is

> > One might argue that this is necessary or even recommendable (introduction
> of
> > more complexity).
> If you're going to have a <doc-type> node, I think it either needs to reside
> in some sort of parameter namespace (which seems messy), or you should have
> to specify it like the following:
> <map:param name="doc-type" map:value="bac.dtd"/>
> or
> <map:param name="doc-type">bac.dtd</map:param>

Sean, I don't see your problem with

 <doc-type map:value="bad.dtd"/>

Each component will have access to configurations and namespaces don't
make it any simpler nor more powerful.

I vote -1 to adding a new namespace for each component. The sitemap will
"consume" its namespace and make available to components everything

I don't see any problem with this.

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

View raw message