Took the time to do a writeup for additional clarity. The below describes the kinds of relationships a character node in the Leo file I'm working on would have, but I'm not sure if this is the right approach. Currently relationships use UNLs to denote which characters they affect in their body text.
--- *Relationship Nodes* A relationship node should only contain other relationships. This is to show that this relationship spawned other relationships. Do not clone any nodes that aren't relationships into them. There are a few kinds of relationships that are important for tracking a character. *Hierarchical Ties* Hierarchical ties show when one character came before the other, or when one character strictly has command over another. Some examples of hierarchical ties include chains of command and families. Technically this should be okay as a tree, but, characters contain a lot of child nodes that are not their offspring or subordinates. Why? Character nodes have data that only concern themselves. It's also impossible to avoid cluttering all the involved people nodes if done that way. *Equal Ties* These are cyclical, but don't have differing data for each viewpoint. Common examples of these include coworkers, friends, and classmates. *Asymmetric* These are cyclical, but different data for each viewpoint. Common examples of these include predator and prey; teacher and student; so on so forth. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
