Search
Forums
Kiwitrees on Twitter
    Tags

    birth, save settings, ID facts, widget, image, kiwitrees, HTML block, follow, 3.1.1, click, spouse, place, bug reporting, xmas, husband, chart, xenea, 2.0.2, add missing death, design, wish, gettext, marriage, custom, emmigration, html, MAC, github, library, merge, backup, login failure, blank, slideshow, date, permissions, fact, person, administration pages, custom modules, spam, calendar.php issue, .mo, webtrees 1.4.4.1, living, sanity, index, MYSQL, cousins, Administration, source, tools, family, dead, age, roadmap, block, media_links, simpl_grey, progress

    #3606
    kiwi
    kiwi
    Keymaster

    1655 posts

    I was referring to the FAM record itself, not to events within it, and thought you were too.

    Officially neither should be allowed, and no event should ever use it, but kiwitrees and webtrees have always broken the event rule and allowed them there.

    The proper use of ASSO is as descibed in the GEDCOM spec. as “An indicator to link friends, neighbors, relatives, or associates of an individual” and “The association pointer only associates INDIvidual records to INDIvidual records.”

    So:

    0 @I7169@ INDI
    1 NAME John /Smith/
    1 ASSO @I1234@
    2 RELA godson
    Totally OK – the only GEDCOM approved use of the tag.

    0 @I7169@ INDI
    1 NAME John /Smith/
    1 BIRT
    2 DATE 21 AUG 2014
    2 ASSO @I8865@
    3 RELA twin
    Allowed by kiwitrees, but not correct GEDCOM

    0 @F7169@ FAM
    1 HUSB @A16702@
    1 WIFE @A9242@
    1 ASSO @I1234@
    Not allowed by kiwitrees and not correct GEDCOM

    0 @F7169@ FAM
    1 HUSB @A16702@
    1 WIFE @A9242@
    1 MARR
    2 DATE 10 OCT 1892
    2 ASSO @I5224@
    3 RELA witness
    Allowed by kiwitrees, but not correct GEDCOM

    Nigel
    My personal kiwitrees site is www.our-families.info