Hi Alex; and first off, thanks a bunch for your feedback on this.
Alexander Klimetschek schrieb: > On Fri, May 22, 2009 at 1:32 AM, Kristian Rink <[email protected]> wrote: >> (b) Use some "reference property" in order to, in a node, keep some UUID or >> path or whatever telling where to find the actual content. > > I'd use a (single or multivalue) string property containing the path > of the reference target. Albeit this requires some extra application > code (especially when the targets are deleted, can be done with > observation), it is the most flexible and transparent approach (paths > are more descriptive than UUIDs and self-made ids need additional > interpretion by application code). Yes, I thought so as well, especially talking about the "descriptive" part of the story. However, that way I lose the idea of "dereferencing" links when using XML export (at least without re-implementing XML export itself manually, that is), am I right? Cheers, Kristian -- Kristian Rink cell : +49 176 2447 2771 business: http://www.planconnect.de personal: http://pictorial.zimmer428.net "Past midnight. Never knew such silence. The earth might be uninhabited..." //beckett / krapp's last tape//
