Agenda

• Antitrust Policy and introductions -  VB
• Identity WG Implementer call - report - 
  • Meeting Notes 2019-11-07+Identity+WG+Implementers+Call Daniel Bluhmor Richard Esplin or anyone who was on the call
• Short talk on FATF beneficial ownership paper.
• LEI PoC using verified credentials
  • http://2019.eurofiling.info/wp-content/uploads/2019-06-18_KarlaMcKenna_GLEIF.pdf

  • The PoC was implemented as follows: 

    1. GLEIF verifies INSEE, the national statistics bureau of France, as a LEI issuing organization (LOU) ) and uses uPort to issue a credential that acknowledges its role as an issuer of LEIs as well as digital credentials for legal entities.
    2. INSEE, upon verification of Societe Generale’s data associated with its status as a legal entity (addresses, subsidiaries, jurisdiction, etc.) and information about its corporate officers (name, role), issues it a credential containing the LEI.
    3. Societe Generale then, as a verified business, issues a role credential to a person acting in an official role. 
    4. These persons now, armed with their digital credentials, are able to sign and submit regulatory filings to regulators, like the Banque de France.
• ID2020: What happened and why is it important Vipin Bharathan
• Discuss  IDWG paper
  
  • Aadhaar section-look at reworked areas - Nitin Agarwal/Kaliya Young
• A GitHub repo was created under Hyperledger for IDWG; Details to follow.
  
• Kiva - current status. After the UNGA- any one from Kiva (Matt Raffel or Camilo Parra )
• Implementing metrics from Chaoss... DCIWG- let us discuss.
  
• Future talks (we are working with some of these folks on nailing down dates)
  • FATF guidance on digital Identity (Stephane Mouy) on the 27th of Nov.
  • A talk by Kim Cameron .
  • A Talk by Darrell O'Donnell on Digital Wallets
  • A talk by Nitin Agarwal on India consent layer - coincident with Jan L in the generic context.

Attendees

Minutes

Anti-trust policy reviewed.

Introductions:

Drummond Reed - evernym Chief Trust Officer. Board member Sovrin Foundation.

Vipin Bharathan - 5 years blockchain. Software industry. Work on systems toward privacy-preserving.

Marvin Berstecher

Richard Esplin - products - evernym. Upstream projects like Hyperledger. Bring into actual code to deploy.

Kelly Cooper - working on Identity White Paper.

Comments on the Hyperledger Identity white paper. 

Drummond - current presentations on Sovrin, etc. 

Sovrin - by December 4, 2019 will submit the data protection revisions to the SVF. Finished 2nd generation in March. Tackled everything except GDPR compliance (DPR compliance). A number of our stewards and customers pointed out GDPR is one set of compliance regulations. Some potential Sovrin customers are governments. Provenances of BC and Ontario, for example. Transaction endorser agreement. Transaction author is anyone who wants to write to the Sovrin Network. Working with BC.gov to close on addressing issues. How does SSI, which is ultimately backed by blockchain immutable ledgers, GDPR rights of data subjects (right of erasure). In systems like Sovrin, there is very little on the ledger. Widely acknowledged even a DID, if it identifies an individual (even pseudonymous) is subject to GDPR. Eight documents involved. Contract - transaction author agreement. Sovrin as a legal representative of the stewards as a whole. There will be a web page, there currently is a diagram. 

Three roles GDPR sets out. GDPR did not anticipate SSI where the ultimate data controller is the individual. Individuals and Things will eventually be able to write to the ledger. Two policy paths, the only path today is permission write access. Driving toward public write access. Now, need to go through Transaction Endorser > Steward > you submit a proper transaction that is validated and it goes on the ledger. In public, transaction authors write directly to the ledger via the Stewards, with a fee (no commitment to Sovrin tokens or dates - only future possibility).

Revisions to the SVF. The legal analysis arrived at is to say, the role of the Sovrin Foundation is not as a data controller; transaction authors are the data controllers. The role of SF is something called a joint controller that does not have control; for legal purposes called a designated data controller. Stewards have contracts for SF. Transaction authors and transaction endorsers - SF transaction author agreement.