> I wish to be able to clearly and succinctly identify the sources, > and logic used to establish a parent child relationship. This is not > usually as simple as citing an individual source, but for me often > requires establishing a "network" of interlocking bits of evidence. > This does not seem to be supported in many Genealogy programs, and > I've been told that the reason for that is that the capability is > not built into the GedCom standards. > > If that's the case, then this would seem to be a severe problem. I > can't think of anything more important than establishing parent > child relationships. > > Can anyone confirm that this is in fact a limitation in the GedCom > standards? > > Quolla6@gmail.com The GEDCOM standard supports the specification of one of four types of relationship of child to a family (PEDI tag subordinate to FAMC tag). These are: birth, adopted, foster, sealing. (Sealing is an LDS ceremony of adopting a child into a family.) Also, there is an "ADOP" event available for each individual. This may contain the reference to the family which adopted the individual (FAMC sub-tag) and a sub-tag (ADOP) to specify which or both parents as HUSB, WIFE or BOTH. Thus: 0 INDI @I1@ 1 FAMC @F1@ 2 PEDI adopted 2 NOTE As and if required. 3 SOUR ... 1 ADOP 2 FAMC @F1@ 3 ADOP HUSB .... 0 FAM @F1@ 1 CHIL @I1@ .... There are a small number of programs that support these tags as defined. Some others define custom _MREL and _FREL tags within the family record to define the relationships of an individual to "father" and "mother" of a family. Note that custom tags may not transport reliably between programs. With respect to sources, the GEDCOM standard does not permit SOUR as a sub-tag of PEDI, but it does permit SOUR as a sub-tag of NOTE as a sub-tag of PEDI. Nigel www.tcgr.bufton.org "Nigel Bufton" <nigel@bufton.org>

> > I wish to be able to clearly and succinctly identify the sources, > > and logic used to establish a parent child relationship. This is not > > usually as simple as citing an individual source, but for me often > > requires establishing a "network" of interlocking bits of evidence. > > This does not seem to be supported in many Genealogy programs, and > > I've been told that the reason for that is that the capability is > > not built into the GedCom standards. > > > > If that's the case, then this would seem to be a severe problem. I > > can't think of anything more important than establishing parent > > child relationships. > > > > Can anyone confirm that this is in fact a limitation in the GedCom > > standards? > > > > Quolla6@gmail.com > > The GEDCOM standard supports the specification of one of four types > of relationship of child to a family (PEDI tag subordinate to FAMC > tag). These are: birth, adopted, foster, sealing. (Sealing is an > LDS ceremony of adopting a child into a family.) > > Also, there is an "ADOP" event available for each individual. This > may contain the reference to the family which adopted the individual > (FAMC sub-tag) and a sub-tag (ADOP) to specify which or both parents > as HUSB, WIFE or BOTH. > > Thus: > 0 INDI @I1@ > 1 FAMC @F1@ > 2 PEDI adopted > 2 NOTE As and if required. > 3 SOUR ... > 1 ADOP > 2 FAMC @F1@ > 3 ADOP HUSB > .... > 0 FAM @F1@ > 1 CHIL @I1@ > .... > > There are a small number of programs that support these tags as > defined. Some others define custom _MREL and _FREL tags within the > family record to define the relationships of an individual to > "father" and "mother" of a family. Note that custom tags may not > transport reliably between programs. > > With respect to sources, the GEDCOM standard does not permit SOUR as > a sub-tag of PEDI, but it does permit SOUR as a sub-tag of NOTE as a > sub-tag of PEDI. > > Nigel > www.tcgr.bufton.org > "Nigel Bufton" <nigel@bufton.org> From Nigels response to my question it appears that a) The GedCom Standard does not directly provide a tag that allows you to explicitly explain the basis on which a family relationship is established. b) To handle this you have to use the notes Consider a website or desktop package that allowed GedCom uploads and downloads. Even if it provided for the capability to explicitly explain the basis for identifying the basis for a parent child relationship (other than through a general note), you would not be able to re-export that information through a GedCom. Thanks to all who replied. I appreciate the information received from all. Q Q <quolla6@gmail.com>