SOUR.PAGE and REPO.CALN do not include examples of useage for web based sources

[Norwegian-Sardines]

Web based source should explicitly be included in the definition of SOUR.PAGE and REPO.CALN definitions.

Proposed changes:

PAGE (Page) g7:PAGE

A specific location within the information referenced. For a published work, this could include the volume of a multi-volume work and the page number or numbers. For a periodical, it could include volume, issue, and page numbers. For a newspaper, it could include a date, page number, and column number. For an unpublished source or microfilmed works, this could be a film or sheet number, page number, or frame number. A census record might have an enumerating district, page number, line number, dwelling number, and family number. For a website source page this could be the full path location to the web source.

It is recommended that the data in this field be formatted comma-separated with label: value pairs

microfilm example

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

web page example

2 SOUR @S1@
3 PAGE URL: http://example.com/sourcepage.html

If the superstructure's pointer is @void@ then there is no information referenced and the PAGE may describe the entire source.

example

1 DSCR Tall enough his head touched the ceiling
2 SOUR @VOID@
3 PAGE His grand-daughter Lydia told me this in 1980

CALN (Call number) g7:CALN

An identification or reference description used to file and retrieve items from the holdings of a repository. Despite the word "number" in the name, may contain any character, not just digits. This reference could include a Uniform Resource Identifier.

It is recommended that the data in this field be formatted with label: value pairs

URN example

2 REPO @R1@
3 CALN URN: ISBN:0451450523

URL example

2 REPO @R1@
3 CALN URL: http://example.com/sourcepage.html

[dthaler]

Discussion during GEDCOM Steering Committee meeting 23 MAY 2024:

• This is a good discussion and we agree that the SOUR.PAGE example with URL is valid.
• The CALN example might be better not having the URN: or URL: prefix, since unlike SOUR.PAGE there is no current recommendation about using name/value pairs there.
• There could be a future request for v7.1 to add an explicit way to have a URL in a SOURCE_CITATION and SOURCE_REPOSITORY_CITATION.
• We think this would be a good thing to add to the FAQ now, while we continue to discuss whether it makes sense to add into the spec itself.

[Norwegian-Sardines]

In case it matter, the software I use, a web based program with a large international usage, currently allows for a URL in both SOUR.PAGE and REPO.CALN, although without requiring the preceding URL: label!