If you're going to do tags you might want to have a look at [1]. It's how we are planning to do content (and tags) and from an abstract point of view looks quite nice.
Simon [1] http://confluence.sakaiproject.org/display/KERNDOC/KERN-554+File+Content+Tags+and+Hierarchy On 24 Jun 2010, at 11:58, Bertrand Delacretaz wrote: > Hi Federico, > > On Wed, Jun 23, 2010 at 7:53 PM, Federico Paparoni > <[email protected]> wrote: >> ...the report of GSoC project.. > > Thanks! > I'm in conferences until the end of this week, will review your code > early next week and discuss the next steps with you. > >> ...*Problems*: The script defined to list the contents submitted ( >> http://code.google.com/p/davidgsoc2010/source/browse/trunk/src/main/resources/initial-content/apps/david/list.esp) >> has always a strange behaviour.... > > If that's still not working after adding resource types to the > *content* nodes (not to the scripts) as I suggested before, please ask > on list in a separate threads, with sufficient information for us to > reproduce your problem. > >> ...*Perspectives*: After the pdf extension, I would like to manage tags for >> entry submitted. I think it's an easy task using multi value properties on >> the node. Then it could be possible to define a search using title and/or >> tag values... > > Tags are a great idea, and we should discuss their JCR content model > at some point. If you can do a first prototype, as simple as possible, > that would be a good basis for discussion next week. > > -Bertrand
