-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ambiguity around month "code" vs tag #570
Comments
Discussion during GEDCOM Steering Committee meeting 19 NOV 2024:
|
Clarifies relationship with standard tags used in the ABNF Fixes FamilySearch#570 Signed-off-by: Dave Thaler <[email protected]>
Clarifies relationship with standard tags used in the ABNF Fixes FamilySearch#570 Signed-off-by: Dave Thaler <[email protected]>
Clarifies relationship with standard tags used in the ABNF Fixes FamilySearch#570 Signed-off-by: Dave Thaler <[email protected]>
Clarifies relationship with standard tags used in the ABNF Fixes FamilySearch#570 Signed-off-by: Dave Thaler <[email protected]>
Clarifies relationship with standard tags used in the ABNF Fixes FamilySearch#570 Signed-off-by: Dave Thaler <[email protected]>
Clarifies relationship with standard tags used in the ABNF Fixes FamilySearch#570 Signed-off-by: Dave Thaler <[email protected]>
Clarifies relationship with standard tags used in the ABNF Fixes FamilySearch#570 Signed-off-by: Dave Thaler <[email protected]>
extensions.ged has an extension tag (
_JOUR
) with a standard calendar (FRENCH_R
):Section 2.4 (Date) of the GEDCOM spec says:
Section 6.1 (Known Calendars) says, under
FRENCH_R
:Taken together, this can be read as saying that the
FRENCH_R
calendar constrains the set of month tags as only permitting ones in the table in section 6.1, such that extension tags are not permitted.Does the extensions.ged file have an invalid test case or does the spec need to be updated?
The text was updated successfully, but these errors were encountered: