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