Page Comparison

...

1. Review of receipt fields. Everyone should review spreadsheet which is in the files folder 
   1. https://kantarainitiative.org/confluence/display/WA/File+lists
   2. Editable spreadsheet for review: https://docs.google.com/spreadsheets/d/1rxF6yym3CGUgtt-AWbrShpazULkSGj9TH1hPxzaF9h8/edit?usp=sharing 
2. Narrative
   1. Mark's Update
   2. Mark's Update
      1. Consent is the framework for notice, provided update in Framework Doc
      2. Vectors of consent and current crosstalk
      3. Explicity legal notice
      4. Use the receipt more than once
      5. Decentralized data governance across architectures
      6. Use receipt as a token 
      7. Rights profile 
      8. Delegation component necessary for the identity management community, can't generate delegation from identity management
      9. EU Privacy Directive Update https://edpb.europa.eu/news/news/2021/edpb-edps-adopt-joint-opinion-data-governance-act-dga_en
   3. Blog Post
      1. Initial brief post up
   Delta 1.1.
   1. 1. Contribution from last week sets baseline.
   2. Blog Post
      1. Initial brief post up
3. Delta 1.1. (Discussion on the Call) and work on the above field spreadsheet, as per below) 
   1. List of fields last week, are a very mature contribution
      1. GDPR Extension
         1. Published Notice Paper (Mark and Harsh)
      2. ISO related contributions
         1. Update with Data Privacy Vocabulary
      3. Pursuit of Legal 
   2. Combine this with 1.1.
   3. Any other contributions.
      1. Child as data subject bias because of requirements and high risk.
         1. Data subject is not capable of an assessment or authorization of data release,
         2. Example of delegation with the Principal (inactive -incapable)
         3. How to record vs. how to collect/enact (implicit consent by delegation).
      2. FHIR ontology into DPV, examples of delegate roles
      3. Delegation of Notice and Consent for Identity service vs. by the identity services
      4. Transborder flow specific fields (extended discussion)
         1. What an individual needs to do to cross any jurisdiction
         2. Not just nation state boundary
         3. Jusrisdictional relationships and nesting.
         4. Two fields for now as optional
         5. Example of expiration of privacy shield
      5. Drives simplified user experience and leaves behind an aritifact useful to both subject and controller.
      6. Privacy Nutrition at Apple vs. simply Nutrition Label → historically static, next gen is active ← back to the WG future...
      7. Attached to substrate of federation protocol
         1. DID is subject of relying party
         2. W3C uri schemes
         3. Side effect of UMA AS. (assumes presence of user in the flow, can perhaps address that in user not present use cases)
         4. Protocol binding as pointer
   4. Discussion of Consent ID
4. Open issues
5. Admin Workflow and Resources
6. Formalize work plan
   1. Expand group participation, open to all
   2. Presentations from abcd to 
7. ISO input
   1. Consenet record structure
   2. DPV for semantic harmonization and consent vectors
   Elections
   
   1. The inaugural officers were all voted into 1 year terms.Motion Jan, unanimous vote.Not discussed
8. Use Cases
   1. Airside (Peter)
   2. Immunity Passports
   3. PaECG

...