GEDCOM 7 SOURCE structure has no WWW tag (for internet links)

[augean]

GEDCOM 7, SOURCE_RECORD structure has no WWW tag A lot of source information is being found on the internet

I wish to record this in the SOURCE_RECORD structure so can you add a WWW tag,

for example, see https://gedcom.io/specifications/FamilySearchGEDCOMv7.html#SOURCE_RECORD

where is the WWW GEDCOM tag ????

I often have internet links as the source, so, please can we add a WWW tag to the GEDCOM 7 SOURCE_RECORD so I can add internet links

(Note the WWW tag, is just a single field, to allow you to enter a URL, for example http://www.ancestry.com/record1234567

Thanks !!!!!!!!!!!!!!

[dthaler]

The <<EVENT_DETAIL>> structure allows a WWW tag, which means all events and attributes on individuals and families can use the WWW tag. I have no idea why it's there though instead of in a SOURCE_RECORD or SOURCE_CITATION.

It does seem odd to me for EVENT_DETAIL to have

n PHON <[Special](https://gedcom.io/specifications/FamilySearchGEDCOMv7.html#cb28-1)>                           {0:M}  [g7:PHON](https://gedcom.io/specifications/FamilySearchGEDCOMv7.html#PHON)
n EMAIL <[Special](https://gedcom.io/specifications/FamilySearchGEDCOMv7.html#cb28-1)>                          {0:M}  [g7:EMAIL](https://gedcom.io/specifications/FamilySearchGEDCOMv7.html#EMAIL)
n FAX <[Special](https://gedcom.io/specifications/FamilySearchGEDCOMv7.html#cb28-1)>                            {0:M}  [g7:FAX](https://gedcom.io/specifications/FamilySearchGEDCOMv7.html#FAX)
n WWW <[Special](https://gedcom.io/specifications/FamilySearchGEDCOMv7.html#cb28-1)>                            {0:M}  [g7:WWW](https://gedcom.io/specifications/FamilySearchGEDCOMv7.html#WWW)

That is, I don't know what it means for an event or attribute to have an email address or fax address associated.

[Norwegian-Sardines]

I'm assuming that you need to have a link to a page on a website to build a citation. I use the four components of GEDCOM (Source-Citation, Source_Record, Source_Repository_Citation, and Repository) to build citations (footnotes, bibliographies) in the same way for all entities books or online.

For a Book Footnote, I would need the basic data points of: (Book Title, Author, Publisher, Page Number). This information would be located in the GEDCOM using (SOUR.TITL, SOUR.AUTH, SOUR.PUBL, Source_Citation.PAGE)

For Online sources I would do the same! The "Where in Source" (Source_Citation.PAGE) would be the logical use for a webpage for the citation. Therefore I put the link in the Source_Citation.PAGE tag. Since we are building a citation, all citation specific data should go in the Source_Citation Structure.

I personally believe that the definition of Source_Citation.PAGE should include the ability to contain a URL. Since the PAGE tag in the v7 Standard provides this example:

2 SOUR @S1@ 3 PAGE Film: 1234567, Frame: 344, Line: 28

It could also include this as an example: 2 SOUR @S1@ 3 PAGE URL: https://www.website.com/grandma_info

[dthaler]

n EMAIL <Special> {0:M} g7:EMAIL n FAX <Special>

Discussion in GEDCOM Steering Committee 1/18/2024:

• These were originally in an earlier GEDCOM specification, without explanation. E.g., EMAIL was added in 5.5.
• Original intent seems to be that they were contact information for the individual or family at the time of the event
• WWW under EVENT_DETAIL is more a property of the individual or family, at the time of the event, than about the citation of where you found the data

[Norwegian-Sardines]

Does “next minor” mean you will be adding the additional Note indicating the use of the URL in the PAGE tag as I indicated above?

[tychonievich]

Discussed in steering committee 23 JUL 2024

Does “next minor” mean you will be adding the additional Note indicating the use of the URL in the PAGE tag as I indicated above?

The "next-minor" tag is used for any proposed action that cannot be done as a patch (in 7.0.x) and probably could be done as a minor version (in 7.x). Often these issues are still in need of discussion and design before inclusion, and the tag is not a promise of inclusion.

If a decision to include it is made, it will be added to the v7.1 branch