On Fri, Apr 24, 2009 at 6:32 PM, Bertrand Delacretaz <[email protected]> wrote: > 2009/4/24 Juan José Vázquez Delgado <[email protected]>: >>> ...See also rule 5 of David's model [2]. >> >> Right, but if tags are deleted or their names modified you´re forced >> to search the path tag properties over all the repository and fix the >> affected nodes. It seems an important drawback. WDYT?... > > It's a drawback, but we feel the advantages (content agility) outweigh > the drawbacks (need to handle some rare stuff at the application > level).
Right. We are doing this in a "lazy" way through the use of an observation listener for the "tags" property on the content. Whenever this is changed, which can happen much later than the modification of the tag tree at /etc/tags, it is validated against the defined tags under /etc/tags. When reading the tags property, there is an application-level utility that filters out non-existing tag. We are also planning to use this lazy approach for restructuration of tags, eg. moving or merging. This also solves the conceptual problem of two very different permission areas: tag administration and content editing. Ok, that's enough of the details ;-) Regards, Alex -- Alexander Klimetschek [email protected]
