GedCom standards
Quo...@gmail.com
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?
Bob Velke
Like many things involving GEDCOM, it depends on your
interpretation. GEDCOM 5.5 does not support a citation for a
specific father-son relationship, for instance. However, it does
support source citations for the "family structure" which includes
both parents and all children. The text of each citation could
arguably specify which binary relationship is being documented.
But if GEDCOM does not support something which you think is critical
for your research, is that a good reason for your software to not
support it?
GEDCOM is the lowest common denominator. If you are willing to
limit yourself to data which is supported by (or, let's say,
reliably transferable by) GEDCOM, then you'll be missing out on a
whole lot more than relationship citations.
Bob Velke
Wholly Genes, Inc.
Bob Velke <bve...@whollygenes.com>
Steve Hayes
GEDCOM does seem to require the forming of "family groups".
The program I use for initial entry, Family History System (FHS)
does not require this. You establish the parent-child relationship
by inserting the father and/or mother's ID in the "Father" and
"Mother" fields respectively. You don't have to "marry" the father
and mother first, as most other genealogy programs require.
When the data are exported to GEDCOM, the routine reports "x family
groups created" -- the program has to create them for the GEDCOM
format.
--
Steve Hayes from Tshwane, South Africa
Web: http://hayesfam.bravehost.com/stevesig.htm
Blog: http://methodius.blogspot.com
E-mail - see web page, or parse: shayes at dunelm full stop org full stop uk
Steve Hayes <haye...@hotmail.com>
cecilia
> 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
>
> Quo...@gmail.com
One could create one's own Source (<my name> conclusion nnnn] with
Source Text explanation of what bits of evidence were combined to
reach the conclusion.
SHARON Zingery
> 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.
> 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?
>
> Quo...@gmail.com
When I am citing my logic on determining that X is the son of, or
wife of, etc., I cite my thinking and my sources in my notes
section.
Nigel Bufton
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" <ni...@bufton.org>
Q
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 <quo...@gmail.com>
Nigel Bufton
I should have added that the ADOP event permits SOUR sub-tags and a
custom EVEN event could be created for Fostering (or any other
event), which itself may have SOUR sub-tags. Therefore, if you
specify events for individuals defining the establishment of the
(additional) family relationships, SOUR sub-tags may be freely used
for each event.
Nigel
"Nigel Bufton" <ni...@bufton.org>