Note two things though: 1) the *aspects* of relations I use are general, abstract terms applicable to any context/relation; you just designate the particulars of any given context as particular instances (with their own particular gnx's) of these general aspect terms (space, location, use type, link type, etc.).
2) the attributes are esoteric to particular contexts/relations I use "relations" more in the database sense, rather than the way you used the term in your other post today -- such that trees/maps are a parent record (root node) with multiple child records related to it. I generalize it more, saying it's not just parent and child (one/many) table entities, but numerous aspects that define more characteristics of the one-to-many relation. This is a different data model, a way I would do a big data database backend for distributed mindmaps. I only see it as of possible interest to you as a way to conceptualize the problem of distributed clones. But as ever, it's a way off from your technical situation; you can contemplate it as you wish, only if some part of it grabs you. Seth On Sun, Sep 4, 2011 at 11:45 AM, Edward K. Ream <[email protected]> wrote: > On Sat, Sep 3, 2011 at 12:21 PM, Seth Johnson <[email protected]> > wrote: > >> You are very far from moving in this direction technically, but I >> thought I'd give you a few notes related to this bit of musing that >> might lead to some useful reflections and insights: > > Thanks for these comments. My present thinking is that gnx's relate > solely to the node identify that Leo has always supported. All other > attributes are "temporary" and "mutable". That doesn't make those > attributes useless in any way. > > The *representation* of these temporary and mutable attributes would > be via clones, implemented as usual with "permanent" (until deleted) > identity (gnx's). These clones would be created when Leo reads the > .leo file containing the attributes. > > This scheme gives us everything we want: attributes can change, but > while they are in effect they create clones as usual. It's quite like > a dynamic clone-find-all command, except that the attributes specified > can be more general than a search pattern. > > Edward > > -- > 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. > > -- 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.
