OFBiz Content Management - i18n - Understanding relationships and best practice

[c.schinzer]

All,


I am trying to get behind the way OFBiz uses the possible relationships
between Content objects. I am trying to enable three different types of
policies within my site and the various sections need to be editable by
diferent people to give the resulting page

Here is my (desired) content hierarchy:

WebSiteCONTENT -- the root publish point
 |
 +- WebSitePOLICIES
 |   |
 |   +- Policy1 (ContentAssoc-type SUB_CONTENT)
 |   |   |
 |   |   +- Policy1Section1 (ContentAssoc-type SUB_CONTENT)
 |   |   |   +- Section1DE -- connects German language version Data Resource
of policy1section1; has mapkey for "policy1section1"
 |   |   |   +- Section1EN -- connects English language version Data
Resource of policy1section1; has mapkey for "policy1section1"
 |   |   +- Policy1Section2
 |   |       +- Section2DE -- connects German language version Data Resource
of policy1section1; has mapkey for "policy1section2"
 |   |       +- Section2EN -- connects English language version Data
Resource of policy1section1; has mapkey for "policy1section2"
 |   +- Policy2 (similar to Policy 1)
 |
 +- (other content for WebSite, e.g. Forums, Blogs etc.)

My questions are as follows:
(1) When rendering, how are the mapentries found? Is it ok to have the
different language versions referring to the same map entry? (btw: I have
changed the FTLs to lookup my mapkeys).
(2) Is it ok to model the various localized versions using the "SUB_CONTENT"
relationship on ContentAssoc? Should it rather be a "INSTANCE" type?
(3) Is ContentAssoc between Policy1Section1 and Section1DE (and the others)
needed at all or would a reference on the Content.instanceOfContentId
attribute in the Content-definition of Section1DE be sufficient?

I will be playing around with these options myself to find out, but it would
be of great help to get some hints on how OFBiz is expected to behave. The
documentation on
   http://docs.ofbiz.org/display/OFBENDUSER/Content+Management+Overview
unfortunately lacks details for the Content.instanceOfContentId attribute as
well as details on the ContentAssoc attributes (especially explanations of
ContentAssoc.contentAssocTypeId values).

Thanks for any guidance :)
Regards


Carsten