I have the same kind of need for best practices about how to model the data, so like you say when to use entity relations, nesting, roles, entities, events etc. I cannot find usable examples or tutorials. I will tell you what I found untill now, I'm still experimenting. Maybe this could help someone, it helps me a little. In the version 1 manual and on the support site I found some definitions but this is just a start, not enough for me. I found a standard for modeling these data, it looks like that the designer of Aeon Timeline knows or even used this standard in some way. The standard is called CIDOC Conceptual Reference Model (CRM) with Ariadne-extended CRM. The standard is used for applications in this area, too in the area of Linked Data and GIS. In the standard they have defined and structured Entities in types (Entity Types) and in Entity Relations. The Event is here an Entity Type just like Place and Person. Different Types of Places are defined like Location or Administrative Division. Too for Person, like Leader, Participant and Observer. In Aeon Timeline Place and Person is a used Entity Type and the different types for Person or Place can be defined with Roles. The Events can have relations with other Entities like Place or Person via the Role, and Events can have relations with other Events via dependencies and Nesting. Strange enough the Role name in Aeon must be unique although it is a Role of a specific Entity Type (I think this could easily be changed be using an Id and not a name for identification). For Role names I use now the name convention EntityTypeName_RoleName. I wish that Aeonline uses even more from the standard, in the current version the Event is a special Entity Type with much more configuration possibilities then Aeon Entity Types. Just reading this helps me to model the data better with Aeon Timeline. I still have a lot to learn, I like the program. I hope maybe others with more experience can add something about the subject of datamodelling with Aeon Timeline.
Thanx very much for the reply...I will take a look at that standard!