also_known_as should be more structured than a simple string

[Julian White]

also_known_as is used to provide additional names the person maybe known as, however its just one of the them, and a string.

Suggest this might be more useful as an array of names, as there maybe more than one, and that the name should have the same construct as in the claims, e.g. with given_name, familiy_name etc.

For example professional actors may be known by birth name, married name and a professional name all at the same time depending on the context.

[Mark Haine]

I like the suggestiopn and have in fact been working along those lines in the OIX. I have built the following example to help inform the discussion. This could be an additional and optional way of representing ‘name attributes’. There is however additional complexity involved in implementing this sort of structure that may be undesirable for some implementers.

"structured_name": [
    {
        "identifier": "Mr Robert Paulson",
        "type": "name",
        "definition": "OIDC Core 5.1"
    },
    {
        "identifier": "Paulson",
        "type": "familyName",
        "definition": "schema.org"
    },
    {
        "identifier": "Mr Robert Paulson",
        "type": "PersonName",
        "definition": "ISO20022"
    },
    {
        "identifier": {
            "surname": "Paulson",
            "middle name": "Horatio",
            "first name": "Robert"
        },
        "type": "Natural Person Identifier",
        "definition": "ISO24366"
    },
    {
        "identifier": "Mr",
        "type": "salutation",
        "definition": "OIDC4IDA 4.1"
    }    
    {
        "identifier": "Bobby Chuckles",
        "type": "also_known_as",
        "sub-type": "Stage Name",
        "definition": "OIDC4IDA 4.1"
    }    
]

‌

[Mark Haine]

Here is another element that is the first draft of how ro represent a previous name within the above structured_name draft…

    {
        "identifier": {
            "surname": "Smith",
            "middle name": "Lettuce",
            "first name": "Euphegenia"
        },
        "schema_type": "Natural Person Identifier",
        "temporal_status": "previous",
        "legal_status": "legal_name",
        "start_date": "1940-02-29",
        "end_date": "1960-04-01",
        "definition": "ISO24366"
    },

[Takahiko Kawasaki]

I’d like to suggest marking this issue as “on hold” for now. Because there are many possible formats we can devise, it will take much time for us to investigate, discuss and reach a consensus on the format. The time will prevent us from finalizing the IDA specification in the foreseeable future.

In addition, personally, it is difficult to imagine that there are many use cases where also_known_as is “verified” by official evidence and the complex structure of also_known_as is critically demanded. Therefore, I doubt that the breaking change (changing the type of also_known_as from string to JSON object) can get support.

[Torsten Lodderstedt]

I support Taka’s position.