Party identification

This part of the iSHARE Trust Framework is considered normative and is therefore compliant with RFC 2119.

In order for parties to identify other parties, any party fulfilling a role in an iSHARE based Data Space MUST provide a unique identifier. The following rules apply:

• Each Data Space MUST select one or more appropriate legal entity identifier(s) used for identification of participants in the data space. It MAY define its own identifier for use within the data space, keeping following in mind:

  • The identification (number/string) MUST be unique for each participant of the Data Space

  • There will be no predefined list of approved identifiers published by the Scheme Owner

  • The use of a DID-method is advised, but other methods including self-defined methods are also allowed.

• Each participant of a Data Space MUST be provided with an iSHARE-ID, which is derived with following considerations:

  • The iSHARE-ID will be provided in the form of an iSHARE DID

  • The iSHARE-ID uniquely identifies an iSHARE participant across data spaces

  • The iSHARE-ID must be provided to the participants by the first iSHARE Satellite where a party onboards

  • The iSHARE-ID will be equal to the organization identifier in an attribute of PKI certificate of the participant. alternatively, for the parties onboarded via the certified identity providers without PKI certificates, the organization identifier MUST be equal to organization identifier provided by identity provider.

Note

For example, when Participant is onboarded using and eIDAS certificate, the identifier in the Subject of the eIDAS certificate is in the ASN.OID - "2.5.4.97" or commonly known as OrganizationIdentifier (issued by a Trust Service Provider (TSP)), with the format of this field described in ETSI EN 319 412-1 V1.5.1, paragraph 5.1.4.

The party identifier will be stored in the form of an array and contain any number of identifiers. An example value is:

[
    did:ishare:EU.NL.NTRNL-12345678,
    did:elsi:LEIXG-724500AZSGBRY55MNS59,
    did:web:example.com
    dataspace_selfdefined_identifier:123456
    kvk:12345678
    eori:EU.EORI.NL123456789
    ...
]

The iSHARE DID method is specified on https://did.ishare.eu/.

Note on backwards compatibility Any existing participants that have been registered with an EORI number will be migrated and the EORI number will be kept in the party identifier array eori:<existing eori number>.