From: Eero T. <ee...@us...> - 2006-01-02 22:08:35
|
Hi, On Monday 02 January 2006 05:19, Don Allingham wrote: > Alex and I have been discussing trying to improve the whole > address/location/place issue. > > Currently, a Location is a set of information about a place. > > A Place is a collection of Locations. The idea is that a single place > can have different identifications. For example, I grew up in a town > named "New Carlisle", but earlier in its history it was know as > "Monroe". Similarly, country boundaries in Europe changed with time. If > you have a person who lived in Prussia, you may want to associate that > with the current location. > > Addresses are similar to locations, except they have a time frame > associated with them. This allows you to specify when a person lived at > a particular place. > > We are looking to combine this in some manner, we just have not figured > out the right way to do this. Ok, I added locations inside place objects. (and Julio answered to questions about Family.) Here's an updated list of primary objects and what kind of secondary object *lists* they can have. (I consider non-list secondary objects to be too much of detail to be shown in a high level diagram) Person: - Names - Addresses - Urls - Attributes Family: - Attributes Places: - Urls - Locations Medias: - Attributes Events: - Witnesses - Medias Sources: - "Data items" Repository (no secondary object lists) What are "Data items" and how they differ from Attributes? Attached is a slightly updated diagram, it doesn't yet contain all the secondary objects from the list above (it's getting late :)). Am I right in my assumption that all relations between primary objects are of the many-to-many type? - Eero |