Initial commit

README.md

@@ -0,0 +1,25 @@
+Names are hard, as summarized in the oft-quoted article [Falsehoods programmers believe about names](https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/).
+
+The [GEDCOM 5.5.1](https://gedcom.io/specifications/ged551.pdf#%5B%7B%22num%22%3A94%2C%22gen%22%3A0%7D%2C%7B%22name%22%3A%22FitR%22%7D%2C-83%2C311%2C695%2C797%5D)
+standard defined a `PERSONAL_NAME_STRUCTURE`.
+This was refined slightly in [GEDCOM 7.0](https://gedcom.io/specifications/FamilySearchGEDCOMv7.html#PERSONAL_NAME_STRUCTURE).
+It works well for most North-American and some European names, but it unable to properly represent names from many other cultures.
+
+This project has been created to develop the `PERSONAL_NAME_STRUCTURE`,
+with aims of supporting a much wider range of human names and
+of supporting applications that process them.
+
+The following tasks have been identified.  More may be added as the project develops.
+
+1) Document commonly used naming structures for various cultures.
+2) Decide the purpose/functionality of `NAME` records.  This might include: display, sorting, searching, grouping, statistics, etc.
+3) For individuals with multiple `NAME` records, consider how we might sort them, for example using `NAME.DATE`.
+4) For individuals with multiple `NAME` records, consider how to identify a "preferred" name, for example by selecting the first one to occur in the GEDCOM record.
+5) Consider any special handling required for names with spaces, e.g. "St John".
+6) Review existing extensions, such as `_RUFNAME`
+7) Develop a new `PERSONAL_NAME` structure and a roadmap to reach it, taking into account the constraints of semantic versioning.
+
+Contributions are welcome.  Please use
+the [discussions](https://github.com/fisharebest/gedcom-name/discussions),
+the [issue-tracker](https://github.com/fisharebest/gedcom-name/issues)
+or create [pull-requests](https://github.com/fisharebest/gedcom-name/pulls) as appropriate.

call-names.md

@@ -0,0 +1,16 @@
+Call names
+==========
+
+An individual can be known by a given name that is not their first given name, or not any of their given names.
+
+In Germany, the call name (`Rufname`) is one of the official given names.
+It is generally underlined when the name is written in full.
+
+In the Netherlands, the call name (`Roepnaam`) may be one of the official given names, a
+diminutive of one of the official given names, or some other name.
+For example, the full name of the footballer `Johan Cruyff` is `Hendrik Johannes Cruijff`.
+The roepnaam is often written in quotation marks, after the given names.  For example `Hendrik Johannes "Johan" Cruijff`.
+
+In the UK (and elsewhere), individuals can be known by a middle name.
+For example, the full name of the former UK Prime Minister `Boris Johnson` is `Alexander Boris de Pfeffel Johnson`.
+In many cases, the use of a middle name can be a family tradition.

diminutives.md

@@ -0,0 +1,8 @@
+Diminutives
+===========
+
+Many individuals are known by a diminutive of their given name or [call name](call-name.md).
+
+For example, `Richard` might be known as `Dick`.  Either name may be used, depending on the context.
+
+More complex examples might combine multiple diminutives.  For example, `Margaret Susan` => `Peggy-Sue`.

religious-names.md

@@ -0,0 +1,9 @@
+Religious names
+===============
+
+Religious names can be created on entry to a monastery or other religious order.
+For example, `Sister Charlotte`, `Brother Stephen`, or `Pope Gregory`.
+
+Baptismal names may be a replacement for, or an addition to, any traditional names.
+
+The name of a saint can be conferred during a confirmation ceremony.