[Zope3-dev] Re: Better access to APIs in paths

[Barry Pederson]

Shane Hathaway wrote:
> Also, like Steve and Barry are discussing, namespaces don't have to 
> point to HTTP resources. 
> "zope.app.interfaces.dublincore.IZopeDublinCore" is a perfectly good 
> namespace, though it's redundant, since there is already a namespace for 
> dublin core.

Yes, and it's that potentially confusing redundancy which made me think 
something like "tal:adapters" might be better than "tal:namespaces" (and 
one is just as much a new Zope idiom as the other).

I agree that using the real XML namespace "xmlns:foo" idiom would be bad 
since you'd either leave it visible for the client, or have to make sure 
it wasn't used by non-tal attributes before stripping it out.

With "tal:adapters", it would be obvious that it's a completely 
different thing, with no relation to the namespaces of the XML tags or 
attributes that are sent to the client.  So template-writers wouldn't be 
wondering why there are two kinds of namespace declarations in their 
templates.

-----

That said, I still have to commend the underlying idea of specifying 
adapters in a TALES path - and think that the only questions being over 
specific syntax is a good sign.

     Barry