2009/4/24 Juan José Vázquez Delgado <[email protected]>: >> Sounds good, and as Felix says I just wrote a blog entry about this >> yesterday [2]. From that you can see that in Day's cq5 the tags are a >> hierarchy of nodes under /etc/tags, with a specific node type, so a >> tag is indeed a separate resource. > > Bertrand, just a question. You decided not to use references pointing > to tags. Why?. I say this because, in principle, using references > looks a good design.
Because references a) don't scale at the moment with Jackrabbit and b) hard references make your content very unflexible regarding partial copying etc. As Bertrand explains it in his post [1]: <snip> We don't use JCR references, but simply store paths in properties, as this gives us more flexibility when restructuring things. It's hard to say what will happen to those tags, and to the very concept of tagging, over the expected lifetime of our product, so we accept potentially dangling references (and cope with them at the application level) to gain content agility. </snip> See also rule 5 of David's model [2]. [1] http://dev.day.com/microsling/content/blogs/main/cq5tags.html [2] http://wiki.apache.org/jackrabbit/DavidsModel Regards, Alex -- Alexander Klimetschek [email protected]
