2016-11-03 Meeting Notes (CR)

Date

2016-11-03

Attendees

Voting

Non-Voting

 

Quorum Status

Meeting achieved quorum.

 

 

Voting participants

Participant Roster (2016) - Quorum is 4 of 7 as of 2016-10-06

Iain Henderson, Mary Hodder, Harri Honko, Mark Lizar, Jim Pasquale, John Wunderlich, Andrew Hughes

Discussion Items

TimeItemWhoNotes
10 mins
  • Roll call
  • Agenda bashing
Former user (Deleted)

Meeting was quorate

 

25 minFormer user (Deleted)
        • Current version of CR
        • David is having trouble keeping the document internal tables in sync. Slowing down the editing.
        • Review cycles have been too short to make effective use of Word as a commenting tool - David will post up the Google Doc version for this last round of feedback
        • Consent Type field
          • There are too many variations to constrain this field at this time
          • We can include a list of suggested values and observe actual implementations
          • Mark originally saw this field as a boolean "explicit" y/n 
        • Purpose / Purpose Category field
          • Should leave these as-is for now
          • No easy way to reconcile what should go into these fields
        • Human readable / JSON examples
          • Use John's examples since they are already done
        • Simon Crossley - MyLife Digital
          • Very good technical design feedback on the JSON parts
          • Proposed some new fields
            • Issued-At-Time (distinguishes time the consent occurred versus the time the receipt was issued). IAT is a JSON reserved name.
            • Issued-By
            • State / Status
              • Not sure how to handle this - it's not really a point-in-time value which would be typical for a transactional receipt but rather a dynamic value
          • Rename "Consent Timestamp" field to Issued-At-Time
          • Suggested to make some of the fields Object types instead of Strings to allow more flexibility
        • For purpose termination field - could reference NIST SP 800-63-3 privacy metadata
        • PII Confidentiality
          • Is in the list of elements but is not in the Schema
          • Delete this because nobody is using it -> move to V1.1
        • NIST uses "Acceptable Primary Use" and "Acceptable Additional Use"

 

CR Spec publication schedule

Current: call for comments on draft spec commences

Date
Event
Status
September 19Close of business (Pacific) deadline for feedback on spec draft including examples and feedback from implementers. 
September 22WG call to review CR draft structure 
September 29WG call to review CR draft and discuss items needing resolution 
October 6WG call 
October 13WG call 
October 20Candidate draft to WG. 
Decision required if the draft is sufficiently mature to base an IIW session on it.
 
October 27Final working session for WG (with/without IIW comments) on candidate draft 
November 3

Final draft for WG review

 
November 10Working group ballot - must be approved by WG on Nov 10th 
November 15Send doc to the Leadership Council. They must approve it by Nov 30. 
November 30LC Approval decision 
December 1Kantara all member ballot begins. 
January 15 2017Earliest Spec approval dateÂ