> On Thu, Apr 23, 2009 at 10:16 PM, Vidar Ramdal <[email protected]> wrote: >>... In order to make Sling (even) more buzzword compliant, I have been >> thinking about a system for tags. [...]
2009/4/24 Bertrand Delacretaz <[email protected]>: > Sounds good, and as Felix says I just wrote a blog entry about this > yesterday [2]. [...] OK, I'm subscribing to your blog. From now on. Promise. >> ...Accessing a tag's URL would output nodes that have the given tag. The >> list could of course be rendered in different formats (json, xml, >> etc).... > > Good idea, but maybe with a specific selector? [...] True. >> [...] But, Sling being a WEB framework, maybe tags should be a more >> integrated part of the framework.... > I agree with Juanjo, that a tagging system is not a core component. > And I agree with you that it's a common use case, so contrib is > probably the place? The tagging system would then be one or several > bundles, servlets, observation components if needed, etc. Sounds good. There's one thing: It might be useful to let a tag (or a set of tags) only be available for a certain branch of the resource tree. Especially if a repository is hosting content for several independent websites, you'd want each website to have its own tags tree. Do you handle that in CQ5 - if so, how? > [1] http://oreilly.com/catalog/9780596529260/ > [2] http://dev.day.com/microsling/content/blogs/main/cq5tags.html > -- Vidar S. Ramdal <[email protected]> - http://www.idium.no Akersgata 16, N-0158 Oslo, Norway +47 21 531941, ext 2070
