On Mon, 14 Apr 2008 15:31:54 -0700 (PDT) thyrsus <[EMAIL PROTECTED]> wrote:
> <link from="gnx1" cx="4" a="EMOTV" unknAtrr1="foo" /> The issue of whether links carry no attributes at all, or only a (perhaps implicit) "direction" attribute, or any number of attributes, is interesting. If I'm understanding, the current unified nodes proposal is that links carry no attributes (apart from the trivial implicit direction, either child list or parent list). So links have nothing interesting to tell us except where they point. An they can just be a python list of references to nodes. Once you let them carry additional attributes they have to be objects in their own right, like vnodes. The alternative is to use "intermediate" regular nodes to carry link related information when required. For links carrying arbitrary attributes, where upper case are nodes and lower case are links, you could represent something as: A-+-a-B | +-b-C | +-c-D where a, b, and c can tell you things about how A relates to B, C, and D. Vs. links that carry no attributes, again upper case are nodes and lower case links: A-+-x-M-x-B | +-x-N-x-C | +-x-O-x-D I use 'x' for all the links because while they're all separate links, there all just python list entries. M, N, and O are additional nodes used to carry link information. I think the latter's the unified node plan for cases where you need to store information about links. Not trying to illuminate anyone, just working through my understanding to see if it's on the right page. Cheers -Terry --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~----------~----~----~----~------~----~------~--~---
