[Zope3-dev] Re: Better access to APIs in paths (was Re: needing viewsclues - template/title troubles)

Jeffrey P Shell jeffrey@cuemedia.com
Mon, 24 Feb 2003 11:32:14 -0700


On Monday, February 24, 2003, at 10:41  AM, Steve Alexander wrote:

>
>> Is it really necessary to hide what's going on under pseudo-XML 
>> namespace declarations, that people may confuse with real XML 
>> namespaces?  How about something more upfront like:
>> <html tal:adapters="dc IZopeDublinCore; sf IStringFormats">
>> ...
>
>
> Do you mean this?
>
>  <html tal:adapters="dc zope.app.interfaces.dublincore.IZopeDublinCore;
>                      sf zope.app.interfaces.formatting.IStringFormats">
>
>
> Namespaces start to look more attractive to me -- there's an obvious 
> place to look up documentation listed right in the source.
>
> I guess it all depends whether the audience for this feature is 
> happier with namespace URNs or with python module names.

URN's, by my understanding, don't have to be http://.... identifiers - 
they just have to be unique, right?  It's just in the spelling of the 
URN.

I think if it's well documented (ie - clear, concise how-to's), people 
won't care about how the URN's are spelled as long as they know where 
to go to be reminded of the spelling.  It's the act of remembering the 
spelling that's usually the worst part for many people, not the final 
spelling itself, because that's usually copied and pasted from 
documentation to document, and then from document to document.  I 
couldn't tell you the namespace identifiers for TAL right offhand, yet 
all my documents have them.