6.3 Identifying and Describing Names

As indicated in Clause 6.2 it is mandatory to provide at least one name for each Party in the PieMessage. The standard also allows to communicate multiple names for a single Party. Examples for a person born on 9th October 1940 in Liverpool include:

  • John Winston Lennon (his legal name until 1969);

  • John Winston Ono Lennon (his legal name from 1969);

  • John O. Lennon (his abbreviated legal name from 1969);

  • John Ono Lennon (his shortened legal name from 1969);

  • John Lennon (his stage name);

  • ジョン・レノン (his stage name in Japanese Katakana);

  • ジョンレノン (an alternative spelling of his stage name in Katakana);

  • Lennon (a shortened stage name); and

  • Jon Lemon (an incorrect name).

To support multiple names, the PartyName composite requires to provide a PartyNameType. This allowed value set contains, amongst others, values relating to the status and use of the name, such as LegalName, StageName, Pseudonym, Nickname and IncorrectName.

The standard then allows to provide the different strings representing a name, its parts and combinations thereof:

  • The FullName of the Party as well as different segments of the name string such as:

    • KeyName;

    • NamesBeforeKeyName;

    • TitlesBeforeNames;

    • NamesAfterKeyName;

    • TitlesAfterNames; and

  • Multiple ShortNames and AbbreviatedNames;

  • The FullNameAsciiTranscribed.

As some companies and industry standards, for example, the IPI Name Number, identify Parties based on their name, it is also possible in PIE to provide a unique identifier for a name using the NameId composite. 

However, such name identifiers may only be used in a PieMessage if the sender includes multiple PartyName composites for a single Party, and that at least one of these names has an identifier that is different from the identifier allocated to the Party itself. Having multiple names as expressed in one PartyName composite is not sufficient for this. 

The following is therefore not allowed as there is only one name and, consequently, only a PartyId may be used:

DO NOT USE

<Party>

    <PartyReference>P1</PartyReference>

    <PartyId>

        <ISNI>0000000121174585</ISNI>

    </PartyId>

    <PartyName>

        <NameId>

            <ProprietaryId Namespace="PADPIDA2014122301Q">

                           1456</ProprietaryId>

        </NameId>

        <PartyNameType>LegalName</PartyNameType>

        <FullName>

            <Name>John Lennon</Name>

        </FullName>

    </PartyName>

    <PartyType>

        <Value>NaturalPerson</Value>

    </PartyType>

</Party> 

The following use of the NameId is conformant to this standard:

<Party>

    <PartyReference>P1</PartyReference>

    <PartyId>

        <ISNI>0000000121174585</ISNI>

    </PartyId>

    <PartyName>

        <NameId>

            <IPINameNumber>00273545259</IPINameNumber>

        </NameId>

        <PartyNameType>LegalName</PartyNameType>

        <FullName>

            <Name>John Winston Lennon</Name>

        </FullName> 

    </PartyName>   

    <PartyName>

        <NameId>

            <IPINameNumber>00017798450</IPINameNumber>

        </NameId>

        <PartyNameType>StageName</PartyNameType>

        <FullName>

            <Name>John Lennon</Name>

        </FullName>

    </PartyName>   

    <PartyType>

      <Value>NaturalPerson</Value>

    </PartyType>

</Party> 

Additional tags in the PartyName composite can also be provided. They are defined in the XML Schema Definition for this standard.

Search