πŸš€

Voyager Identity #7

Last Edited Time
Jun 13, 2022
Created time
Apr 14, 2022
Participants
Created By
Type
Identity WG
Created
Apr 14, 2022
Property
Property 1
Attendees
  1. Conner Swenberg
  1. Mendes
  1. David Sneider
  1. Balazs Nemethi
  1. Brian Petes
  1. Victor Leipnik
  1. Cent Hosten
  1. Josh Tan
  1. Aaron
Β 
Meeting Minutes
Revocation
Have the consumer of attestation determine if the attestation is acceptable within the expirey date.
BPetes
  • Discussion about interesting combinations
Josh
  • Let’s assume 24hr expiry dates
Β 
To Do
Develop the DAOIP page
  • include the various sub WG contributions.
    Β 
    Clarify:
    If the DAOs are publishing some form of data as a URI, is the issuers issuing a secondary attestation
    We are thinking there there is some way of pointing to some place that says that this entity is attesting this data (could be a DAO or third party issuer)
    More clarity about revocation and expiration
    Β 
    PII
    You should never be attesting to names, but to membership
    Schema can be extended, but they are not recommended
    This might not be the most pure way of managing identity, but we believe this is a way forward at this time, and recommend limiting
    Josh (proposal): Consensus? We’re defining this architecture for NON-PII information linked to an address or digital credential controlled by an end-user or DAO. We do NOT recommend extending the data model on your own.
    We expect all extensions to fit a certain format and ensure that they are auditable to make sure that they are compliant for GDPR
    We might be able to modularize this out of the standard in terms of specification
    Formulate this part of the discussion into a question and pose it to Jimmy in the chat.
    Β 
    πŸš€

    Voyager Identity #7

    Last Edited Time
    Jun 13, 2022
    Created time
    Apr 14, 2022
    Participants
    Created By
    Type
    Identity WG
    Created
    Apr 14, 2022
    Property
    Property 1
    Attendees
    1. Conner Swenberg
    1. Mendes
    1. David Sneider
    1. Balazs Nemethi
    1. Brian Petes
    1. Victor Leipnik
    1. Cent Hosten
    1. Josh Tan
    1. Aaron
    Β 
    Meeting Minutes
    Revocation
    Have the consumer of attestation determine if the attestation is acceptable within the expirey date.
    BPetes
    • Discussion about interesting combinations
    Josh
    • Let’s assume 24hr expiry dates
    Β 
    To Do
    Develop the DAOIP page
    • include the various sub WG contributions.
      Β 
      Clarify:
      If the DAOs are publishing some form of data as a URI, is the issuers issuing a secondary attestation
      We are thinking there there is some way of pointing to some place that says that this entity is attesting this data (could be a DAO or third party issuer)
      More clarity about revocation and expiration
      Β 
      PII
      You should never be attesting to names, but to membership
      Schema can be extended, but they are not recommended
      This might not be the most pure way of managing identity, but we believe this is a way forward at this time, and recommend limiting
      Josh (proposal): Consensus? We’re defining this architecture for NON-PII information linked to an address or digital credential controlled by an end-user or DAO. We do NOT recommend extending the data model on your own.
      We expect all extensions to fit a certain format and ensure that they are auditable to make sure that they are compliant for GDPR
      We might be able to modularize this out of the standard in terms of specification
      Formulate this part of the discussion into a question and pose it to Jimmy in the chat.
      Β