To start - let say I've some content and templates. In the templates I want to address content parts - but not only from the file just being processed. For example I need to make some summary of other articles in the same directory. It would be nice if I could address parts of the other articles in just the same way as I address parts of the current article. So what I suppose is some addressing scheme unifying directory tree addressing with content parts addressing. Since content usually can be structured as tree it is a simple idea to just put those content trees in place of the file leeves in the directory tree and the whole resulting tree put on stash to be accessible by templates.
Actually I've just started some implementation - you can download it by CVS from cvs.perscm.sourceforge.net:/cvsroot/perscm. The whole project is to be some desktop content manager - might be of interest to you for its own. But I'm feeling like I'm duplicating ttree functionality in there. Zbigniew Lukasiak
