Hi Alex, first of all, thanks for your quick response, which gives a nice overview. I already know the collection "David's Model" and tips like nt:unstructured for being more flexible.
However, the things you've pointed out are all related to designing the _content model_. What I'd like to discuss is the "other side", the design of an _application_ which uses this content model. Regards, Florian Ursprüngliche Nachricht vom 02.06.2008 um 15:18: > The classic starting point is David Nüscheler's (JCR spec lead) > content-modeling guide: > http://wiki.apache.org/jackrabbit/DavidsModel > You should design the data model not based on the application code, > but from a content standpoint: what belongs together, what is > read/written together most of the time and how can it be organized > effectively. The latter can always be verified by how easy it is to > browse through the content tree as a human. And the hierarchical data > model (together with less-strict typing, eg. nt:unstructured) gives > you freedom to change the model later (eg. introduce another entity, > ie. folder) - you are not forced to design the perfect model up-front, > as you are more-or-less forced with relational database schemas. > Regards, > Alex
smime.p7s
Description: S/MIME Cryptographic Signature
