Hi, On Thu, Jan 15, 2009 at 11:57 PM, Cheng Zhang <[email protected]> wrote: > Do you guys see any problem here?
Looks pretty good to me. You probably won't need the ASIN property on the Review node, as that can be looked up from the parent. You may want to look at using for example the summary field and perhaps the date as the starting point for generating unique names to the review nodes. This allows you to avoid the same-name-siblings feature, which is often a bit troublesome to handle in practice. A good rule of thumb for converting XML models to JCR is to remember that nodes in JCR are much heavier than elements in XML, so you'll want to map any "data elements" (ones that contain no internal XML structure) to JCR properties. It looks like you're already doing this well. BR, Jukka Zitting
