Note that all my wonderings about these kinds of pubsub configuration would probably join (I think) those of Peter Saint André about blog integration (though I open this discussion to all the pubsub system even though my main example is also about blogs). You can see the discussion in the april discussions of the social list: http://mail.jabber.org/pipermail/social/2008-April/000109.html
One point of this discussion was to organize the pubsub nodes for a blog. For my own, I don't think this is the right question, because I think this should be implementation specific. Not everybody will have the same needs, so the organization of the nodes may be different and efficient depending on the cases (not everyone manages publication the same way). But what is important here is not the final organization, but the "tools" providden to the implementers. Currently the only "tools" are the possibility to organize in nodes, subnodes, etc. like in the whole file system history. This is necessary, but very weak as soon as you want advanced organization, with "stuffs" (the published items, but maybe even container nodes!) belonging to several categories (so a system of category and tag), or why not the possibilities of dynamic nodes (like you can do in http) generated depending on path or options, etc. Directory architecture is nice, especially because it is close to our "material classification system" (you cannot classify a single paper in several file, unless you copy it), but does not give all the "power" which is accessible with current technologies, especially computers. -- Jehan ------------------------------------------------------------------------ Jehan's Profile: http://www.jabberforum.org/member.php?userid=16911 View this thread: http://www.jabberforum.org/showthread.php?t=95
