-
Proposal:
Add a new NamePart known type of:
http://gedcomx.org/Patronymic
Support for pre-surname era of Scandinavia and other place using patronymic names. In the Scandinavian case the "last name…
-
# Executive Summary
The record and conclusion models actually model the same domain but have been artificially separated. Thus, GedcomX isn't even interchangeable with itself in spite of trying to be…
-
Overloading Date with a value of "May 1863 - Jun 1864" is a burdened concept. When needed, which only seems to apply to waypoint time spans and collection coverage, then we should have a DateRange obj…
-
> Note that original and interpreted are not of type FormalValue. I don't think that's necessary, but not everybody's aligned on that yet. I'd invite @carpentermp to open up a separate issue describin…
-
The following commentary was submitted by @ttwetmore, and I'm opening it up for discussion, my comments to follow:
> The GEDCOM X record model has an object called Record. This is an unfortunate name…
-
The following commentary was submitted by user @ttwetmore regarding the "two-tiered" definition of the model:
> The GEDCOM X model is what I call a “two-tier” model because it has two levels, the rec…
-
This approach of having a “www” flavor of an object that has “links” seems to be getting more and more problematic. It is exploding the number of classes (because lots of objects now have a “www” cou…
-
We probably need a model for Notes on a Person (and possibly other entities).
-
The original gedcomx Record is intended to be able to accurately represent original historical documents. In representing historical documents, it may be desirable to represent empty fields as well a…
-
What is the general approach to getting the metadata of a GedcomX entity? I can think of a few options:
1. Append “/meta” to the URL of an entity to fetch the metadata for that entity. I have grown…