Open APIs

Expand all | Collapse all

TMF-632 Additional names for Party

  • 1.  TMF-632 Additional names for Party

    TM Forum Member
    Posted Apr 01, 2019 06:17
    Hi All,

    I have a problem with additional names for party e.g. third name. Neither in old party management specification (R14.5.1) nor in new (R18.5.0) there is no place for additional names.
    There is a structure called otherName, but the description of this field says something different than i need:
    "A list of other names (OtherName [*]). Keep track of other names (for example the old name of a woman before marriage or an artist name)."
    It looks like an container for previous names, not for additional.

    Does anyone have this problem? Thank you in advance.

    Best Regards.

    ------------------------------
    Adam Augustyn
    Comarch S.A.
    ------------------------------


  • 2.  RE: TMF-632 Additional names for Party

    TM Forum Member
    Posted Apr 01, 2019 11:00
    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
    ------------------------------



  • 3.  RE: TMF-632 Additional names for Party

    TM Forum Member
    Posted Apr 03, 2019 11:12
    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.
    ------------------------------



  • 4.  RE: TMF-632 Additional names for Party

    TM Forum Member
    Posted Sep 13, 2021 09:29
    Jonathan-

           In Latin America, last name (father's last name) and second last name (mother's last name) are typically used to identify people. How does the second last name fit into individual Party? Where should second last name be placed?

    -Regards
    Ricardo Tirado Negrón
    Claro Puerto Rico

    ------------------------------
    Ricardo Tirado
    Claro Puerto Rico
    ------------------------------



  • 5.  RE: TMF-632 Additional names for Party

    TM Forum Member
    Posted Apr 04, 2019 06:15
    Hi Adam

    If you think that functional semantics are missing from the API, you are free to extend to meet your specific business needs. Or, if you believe that this would have value to the wider community, raise a change request for API improvement. We welcome feedback from the community since this helps to improve the APIs for the greater good.

    ------------------------------
    Jonathan Goldberg
    Amdocs Management Limited
    ------------------------------



  • 6.  RE: TMF-632 Additional names for Party

    TM Forum Member
    Posted Apr 04, 2019 09:22
    Thank you for your help.

    ------------------------------
    Adam Augustyn
    Comarch S.A.
    ------------------------------



  • 7.  RE: TMF-632 Additional names for Party

    TM Forum Member
    Posted Sep 14, 2021 10:02
    Hi Jonathan, is there a portal that we can use to raise change requests?
    Also, if a change is accepted, I guess it is published in the next version of the API Spec. Would we expect to get a decision ahead of the publication of the next version. Obviously, our designers are keen to press on with their work.

    Thanks in advance, Jeff

    ------------------------------
    Jeff BARKER
    BT Group plc
    ------------------------------



  • 8.  RE: TMF-632 Additional names for Party

    TM Forum Member
    Posted Sep 13, 2021 09:44
    Hi Ricardo
    Over the last few months, I have started to acquire many LinkedIn connections in Latin America, and indeed I noticed that these people tend to have multi-component names, now I understand why :) .
    I don't think that in the core Open API model we want to enhance Individual for this, this would lead us down the path of model localization per region (consider for example different variations of Geographic Address).
    You could add the additional name field as an extension, or you could have an implementation convention that the names used for identification are represented as a single space-separated string in the familyName attribute in the API payload (of course this does not constrain how you would handle the storage of the names in persistence layer).

    Hope it helps

    ------------------------------
    Jonathan Goldberg
    Amdocs Management Limited
    Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
    ------------------------------



  • 9.  RE: TMF-632 Additional names for Party

    TM Forum Member
    Posted Sep 14, 2021 13:00
    @Jonathan Goldberg Try Arabic names, they
    Ism, Nasab, Laqab, Nisbah and if I remember it right, each placeholder can hold multiple names.
    and you could still add maiden name for good measure!

    @Adam Augustyn, I  believe I read TMF does encourage API users to modify them to fit their customary/local or regional/regulatory requirements.
    Generally, I'd prefer such special needs are excluded from the API/SID specifications unless they benefit the larger audience. Hopefully yours will make it.
    There is always the danger of bloating the API.

    My 2 cents
    ​​

    ------------------------------
    Matthieu Hattab
    Altibox AS
    ------------------------------



  • 10.  RE: TMF-632 Additional names for Party

    TM Forum Member
    Posted Sep 14, 2021 10:19
    If you are a member of the Open API collaborative project, then you could use our internal JIRA to raise CRs.
    Otherwise, I guess this message board is the place :)

    ------------------------------
    Jonathan Goldberg
    Amdocs Management Limited
    Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
    ------------------------------



  • 11.  RE: TMF-632 Additional names for Party

    TM Forum Member
    Posted Sep 16, 2021 01:48
    @Matthieu Hattab, @Jonathan Goldberg what do you thing about adding a key-value map e.g. additionalName which could be filled dynamically like characteristics?​​

    ------------------------------
    Adam Augustyn
    Comarch S.A.
    ------------------------------



  • 12.  RE: TMF-632 Additional names for Party

    TM Forum Member
    Posted 30 days ago
    I've used this approach (not in API context but SID) for translations.
    for example, product name, there was no way we would add extra attributes for each new language.
    for char we used language ISO code.

    ------------------------------
    Matthieu Hattab
    Altibox AS
    ------------------------------



  • 13.  RE: TMF-632 Additional names for Party

    TM Forum Member
    Posted Sep 17, 2021 05:16
    We really don't like key-value maps (i.e. Characteristic), since they basically allow the API definition to lose its strong typing. As a pattern we should have Characteristic only when there is a corresponding Characteristic Spec (as in the catalog/inventory entities and in other places). The implication is that the key-value pairs are really not known in advance, since they can be defined dynamically.
    In the case of additional names there is no guesswork - each locale/region has well-known rules for names, and you should use the extension mechanisms to reflect this.

    ------------------------------
    Jonathan Goldberg
    Amdocs Management Limited
    Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
    ------------------------------



  • 14.  RE: TMF-632 Additional names for Party

    TM Forum Member
    Posted 29 days ago
    Specifically for national language translation, we have a separate track running (rather slowly, I'm afraid) where we want to describe in the TMF630 guideline document how to manage translation scenarios.
    Hopefully we'll have some news in the not-too-distant future.

    ------------------------------
    Jonathan Goldberg
    Amdocs Management Limited
    Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
    ------------------------------