Date and Time
...
- Roll
- IPR
- Minutes Approval
- Agenda Approval
- New attendee intros
- Agenda Items Discussion
- Actions pending
- Actions new
- Updates from the consent community
- AOB
Minutes
Roll call
Salvatore D'Agostino (Unlicensed)
PeterD (Deactivated)an Lundquist
IRP Policy Announcement
Quorum was 4 of 5
Approve minutes
- Will wait for updated minutes from 20210203
- 20210224 Mintues accepted
...
Minutes
We will proceed with small, bite size chunks of
...
the deltas from 1.1 with regards to the structure of the core receipt.
Header is the notice component w/controller identity
Legal justifiction
...
then follows from there.
Consent notice receipt
...
represents the base max schema, which is
...
the goals for Vnext of the consent receipt.
Extension follow for example by receipt type, interest notice, and/or contract notice.
Action Narrative
...
Actions
Narrative for the effort of the WG.
Delta 1.1.
...
Open issues
Admin Workflow and Resources
Blog Post
- Workgroup up and running
- Formalize work plan
- Expand group participation, open to all
- ISO input
Intros...
...
- Presentations from abcd to WG
- Presented work to DIACC
- OpenID Paper Submission (Harsh lead)
- ISO input
Review of receipt fields. Everyone should review spreadsheet which is in the files folder
https://kantarainitiative.org/confluence/display/WA/File+lists
Is 1.2 going to be compatible vs. a 2.x, supporting prior version is not a requirement
Shared 27560 fields and categories
Comment that V.next should begin to consider requirements for active notice
PeterD (Deactivated) as an implementer of 1.1. the extensions added in their use case includes time boundaries, association w/terms and use and conditions, as well as privacy policy, semantics around the publication date of the document. Is it possible to get the example from their schema. "On deck is the way back machine for the privacy policies."
Mark Lizar (Unlicensed) on boarding of privacy policy for broadcasting.
Discussion of use cases and the need for each of the fields to support the use case.
Suggestion to make use of the JWS (and JOSE) for the related crypto operations.
Need to consider how we address differences in credential technology, e.g. distributed ledger, vs. others.
Ongoing discussion of legal vs. technical. Critical update area as legal justification is a gap in 1.1.
Workbook
editable spreadsheet for review: https://docs.google.com/spreadsheets/d/1rxF6yym3CGUgtt-AWbrShpazULkSGj9TH1hPxzaF9h8/edit?usp=sharing
Calendar Update
Work Plan (draft)
End of March informal freeze specification and fields, also determine areas for later work, not included in current specification publication.
Early-Mid April (draft for ISO consideration during next comment period)
End of April draft for circulation
End of May consolidate comments
End of June publication
Need to coordinate (and determine) ISO 27560 comments and drafts schedule with that of the workgroup.
Determine any resources we need to support the workgroup and specification publication.
Discussion of election process, desire to have WG leadership roles apart from Chair, Vice-Chair, Secretary, Editor. Open to adding these as the opportunity arises.
As of 17 February Quorum is 3 of 5.