Stefan Seifert wrote > >> I like Stefan's Content proposal but it's really a ContentTree, right? > > to be precise the current "Content" interface represents one node in the tree > - so alternative names could be "ContentNode" or "ContentResource"? >
Sorry for joining the discussion so late, but do we really want to create another tree api? There is the JCR api, we have our resource abstraction, I assume there are even more hidden in the bundles we use and now we want to create yet another one with basically the same methods/behaviour? What is the exact purpose of this module? Or asked differently, what do we expect clients do with the parsed content? Regards Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
