PAFM Naming Work Group
Conference Call Notes
Fifth Conference Call, Thursday, April 15, 16:00-17:30 EST
Attendees:
Tom de Jong | (Holland) | |
Irma Jongeneel - De Haas | (Holland) | |
David Rowed | (Australia) | |
Klaus Veil – Moderator | (Australia) |
Name Context
We reiterated the need for four name context datatype subcomponents (Context ID, Context Description, Context Type Code & Context Type Description) but no suitable datatype has been found. KV to seek advice from Mark Sharfarman if the requirements can be mapped or if a new datatype can be created. In the interim, the CE datatype will be proposed.
David will provide use case material for inclusion into V2.3.2 proposal.
Closure on this issue was achieved.
Partner/Spouse Name Subcomponents
Based on last week's discussions we now have four "family name" subcomponents:
<family name (ST)> & <last_name_prefix (ST)> & <family name of Partner/Spouse
(ST)> & <family name prefix of Partner/Spouse (ST)>
This allows the Name of Partner/Spouse name type "P" to be retired.
There was a lengthy discussion on how the four subcomponents would be populated. Important issues are generality and backward compatibility. Irma & Tom will create detailed examples and descriptions to clarify the use.
Irma raised the issue of names being retained from previous partners/spouses. Although there is no direct need for this in Holland, Irma believes that there are use cases in the US (Priscilla Presley?). Irma will pursue further.
Closure on this issue was achieved.
Nickname / "Call-me"-Name / Streetname
Unfortunately, Mark could not join us to help on this issue. The main concern is that a new name type will create overhead. This contrasts with the universality of a new name type. After some discussion, the universal solution of establishing a new name type "Nick/'Call me'/Street Name" ("N") was acceptable to all.
Irma/Tom to look at which components will be populated in which situation.
Closure on this issue was achieved.
Plan for PAFM TC Meeting in Toronto
We have two half days available for core V2.3.2 work: Tuesday afternoon and Friday morning. (Unfortunately, Tom will not be able to attend Friday.) This proposal will be reviewed within the Chapter 3 work on Tuesday afternoon. KV has agreed with Freida and Mike that the review of V2.3.2 enhancements will be "by exception", ie. The proposed changes will be edited into the V2.3.2 draft 2 and removed if the TC objects to the items proposed. As we already have reviewed part of Ch. 3, we hope to start on Ch. 6 on the Tuesday.
In the Friday session we will focus on completing Chapters 6 and 8, in which not many changes are expected.
Action Items:
There will be no further tele-conferences on this topic before the Toronto Meeting.
![]()