Thank you Jonathan,
In my opinion the OtherName type looks like a container for keeping track of names changes, because it doesn't contain a place where I can put the type of the name and value. Additionally this type contains all fields which are normally in the base party section and a validity period section.
Below is the example from the document 14.5.1.
{
"id": "i42",
"href": "http://serverlocation:port/partyManagement/individual/i42",
...
"title": "",
"givenName": "John",
"familyName": "Smith",
"middleName": "",
"fullName": "",
"formattedName": "",
"otherName": [
{
"title": "",
"givenName": "",
"familyName": "",
"middleName": "",
"fullName": "",
"formattedName": "",
"validFor": {
"startDateTime": "2013-04-19T16:42:23.0Z",
"endDateTime": "2013-06-19T00:00:00.0Z"
}
}
],
...
}
Best Regards,
------------------------------
Adam Augustyn
Comarch S.A.
------------------------------
Original Message:
Sent: Apr 01, 2019 10:49
From: Jonathan Goldberg
Subject: TMF-632 Additional names for Party
Hi Adam
My personal view is that this OtherName type can be used for any purpose, including additional names. The description that you quoted regarding name history says: For Example, and so is not binding, just suggesting a use case.
Hope it helps
------------------------------
Jonathan Goldberg
Amdocs Management Limited
------------------------------