jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Torgeir Veimo <torg...@pobox.com>
Subject Re: Node mapping question: when should I use subnode?
Date Thu, 22 Mar 2007 13:13:08 GMT

On 22 Mar 2007, at 11:54, Jukka Zitting wrote:

>    /my:content
>    /my:content/tags
>    /my:content/tags/<tag>
>    /my:content/users
>    /my:content/users/<user>
>    /my:content/workflow
>    /my:content/workflow/<status>
>    /my:content/content
>    /my:content/content/<yyyy>/<mm>/<question>
>    /my:content/content/<yyyy>/<mm>/<question>/<answer>
> The /my:content root node is for a clean separation from /jcr:system
> and any other content applications you may want to store within the
> same workspace.
> The second level (tags, users, workflow, content) is for partitioning
> your content by type. In future you might want to generalize these
> parts into standalone /my:tags, etc. components that could be used
> with all sorts of content applications.
> Tags would be referenceable nodes with whatever metadata properties
> you may want to associate with them. If you want, you could also have
> a tag hierarchy. Question and answer nodes would have a multivalued
> "tags" reference property that points to the associated tags. The tag
> nodes would be named by the tag name

You'd probably want to store tags by their owners, eg


otherwise you'd have to manage ownership by references, and you'd end  
up with a lot of child nodes under the tags node.

Torgeir Veimo

View raw message