Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

Date and Time

Agenda

  • 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)

...

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 delta, 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 then follows from there.

Consent notice receipt is represents the base max schema, which is requirement for 1.2Then extensible the goals for Vnext of the consent receipt.

Extension follow for example by receipt type, interest notice, and/or contract notice.

Actions

Action Narrative Action delta for the effort of the WG.

Delta 1.1. and open

Open issues

Admin Workflow and Resources

...

  • Workgroup up and running
  • Formalize work plan
  • Expand group participation, open to all
    • Presentations from abcd to WG
    • Presented work to DIACC
    • OpenID Paper Submission (Harsh lead)
  • ISO input

Intros...

PeterD (Deactivated)


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.

...