Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • potential Adhering Party wants to start fulfilling one or more adhering role(s) in the network.
  • A potential Certified Party wants to start fulfilling one or more certified roles(s) in the network.
  • An already Adhering and/or Certified Party wants to expand its current role(s) by one or more role(s) in the network.

The admission process for Certified Parties builds on the admission process of the Afsprakenstelsel elektronische toegangsdiensten.

Note: prospective iSHARE participants can start testing at any moment in time before initiating the admission process.

...

  • Provide a signed iSHARE accession agreement;
  • Provide a valid EORI number (or other nationally recognised chamber of commerce number which can be verified);
  • Provide the certificate a PKIOverheid or Qualified Electronic Seal (under 70222126) that will be used for iSHARE;
  • Provide a successful test report of iSHARE certification tool (or otherwise acceptable proof that party's technical implementation adheres to iSHARE specifications, e.g. in case of using 'iSHARE compatible' software).

...

  1. A representative of the prospective iSHARE participant registers with the Scheme Owner and provides the Scheme Owner with:
    1. Primary contact details: name, role, e-mail.
    2. Description of how they will be using iSHARE
    3. A valid EORI number (or other nationally recognised chamber of commerce number which can be verified);
  2. The Scheme Owner checks whether there are potential impediments that could block the completion of the admission process for the prospective iSHARE participant:
    1. E.g. previous exclusions from the iSHARE Scheme in the recent past;
  3. The Scheme Owner will facilitate testing and certification of the prospective iSHARE participant.
    1. The Scheme Owner may provide testing material and documentation on the Scheme test environment: certificates, keys, SDKs, etc.;
    2. For prospective Certified Parties this will include role-specific non-technical requirements.
  4. The prospective iSHARE participant formally requests admission to the iSHARE network to the Scheme Owner by providing:
    1. An iSHARE accession agreement signed by an authorized representative of the prospective iSHARE participant;
    2. The certificate that you will use for iSHARE;
    3. Acceptable proof that the prospective participant’s technical implementation adheres to iSHARE specifications;
    4. For a prospective Certified Party: The level of assurance for which the prospective Certified Party wants to be certified, accompanied by a filled in Assessment Framework (and related evidence) to prove that the operational processes of the prospective Certified Party comply with the indicated level of assurance. 
      1. If desired, a standard NDA can be signed before providing the Assessment Framework and related evidence. Please request a signed NDA at info@ishareworks.org. 
    5. For prospective Certified Parties additional verification may be required.
  5. The Scheme Owner verifies the acceptance of the prospective participant's admission request and its conformance with the admission criteria;
    1. For prospective Adhering Parties the Scheme Owner has 5 working days to verify the acceptance of the prospective participant’s admission request and its conformance with the admission criteria
    .
    1. ;
    2. For prospective Certified Parties the Scheme Owner has 30 days to verify the acceptance of the prospective participant's admission request and its conformance with the admission criteria, but aims to respond and soon as possible;
  6. A legal representative of the Scheme Owner signs the participant’s iSHARE accession agreement, and communicates the verified acceptance to the new participant;
  7. The Scheme Owner records the participant’s status within the scheme in the iSHARE participant registry.