michelesalvador
commented
7 months ago Good question.
GEDCOM 5.5.1 (page 33) puts the RESI tag under INDIVIDUAL_ATTRIBUTE_STRUCTURE, that means it should have a Value.
But instead of a Value definition (as for other attributes) there is an ambiguous comment:
n RESI /* Resides at */Instead under FAMILY_EVENT_STRUCTURE, RESI is clearly without Value.
My conclusion now is that RESI should not have a Value, neither for person nor for family.
Why did I assign Value to it? I was misled by a comment from Tamura Jones in GEDCOM 5.5.5, saying that "Residence isn't an Event but an Attribute": attributes usually have a Value.
Therefore I will remove Value from Residence!
About Place and Address: yes, their content could clearly overlap. For my knowledge, Place is far more relevant than Address. If you have to choose, use Place. In my researches I usually do like this: Place: Mountain View, California, United States Address: Line 1: 1600 Amphitheatre Parkway Omitting from Address all fields that are already in Place.
Under residence, one can enter an address. The address already contains the city. Then what are the entries VALUE and PLACE for? I used to be lazy and added only the city where someone lived - oftentimes I don't even know the address. Then I simply put the mame of the city into the value field. But maybe I'm doing it wrong. Should it go into place? But what is value then for? And why enter the city twice, namely in value (of residence) and in the address (as city)?
Same under education, you can add a school with address that contains the city and then still have another entry apart which is called place