Revisit representation of personal names

[apdavison]

In the openMINDS developer meeting of 2023-10-02 we discussed changing the representation of personal names, since

• some people have only a single name, no family name
• "givenName" may not be semantically correct, since some people use a name they have chosen themselves, not one that was given to them
• more generally, some people are known by different names at different times in their life

In the short term, we decided to store a single name in the "givenName" property.
In the medium term, we will add an optional "fullName" property (which will be inferred from givenName and familyName if those are given"). This is backwards compatible.
In the longer term, we will make "fullName" required. This requires a new openMINDS major release.

For name changes, we decided to keep using the "alternateName" array.
The alternative approach, of adding a separate Name/NameVersion schema, was felt to be too complicated.

A further topic is whether to represent middle names by (a) making givenName an array, (b) adding a middleName property, (c) as at present, put them as initials in givenName.

[jcolomb]

never ending issue (see #83,#17) :)

new schema in this space by quarto at https://quarto.org/docs/journals/authors.html:
name:
given: string
family: string
literal: string
dropping-particle: string
non-dropping-particle: string

I like the term "literal" which represents the jatsxml "string-name".

As you probably know, Orcid use givenNAme as the required field:
https://support.orcid.org/hc/en-us/articles/360006973853-Add-and-edit-your-name-on-your-ORCID-record

[lzehl]

related to #513

[apdavison]

To keep things simple, I propose to change the instructions, and the entry in properties.json, for givenName, as follows:

_instructions: "Enter the given name(s) of this person, or a name chosen in place of the given name. At least one of the names should be spelled out in full; initials may be used for the others."

description in properties.json: "Name given to a person or chosen by them in place of the given name, optionally including middle names or initials, but excluding the family name."

[lzehl]

add ons to @apdavison comment:

Update description in properties.json also for familyName: Name inherited or shared within a family group, typically indicating lineage or ancestry, and excluding any given or middle names.

familyName instructions: "Enter the family name (surname) of this person, as normally written; do not include given names or initials."

fullName instructions: "Enter the person’s complete name as it is typically written or spoken, combining their given name(s) and family name in the customary order."

Not sure though if we really should use fullName here. Or rather legalName? or registeredName?

[lzehl]

latest comments / decisions for this were included in #561