Skip to end of metadata
-
Created by Former user (Deleted), last modified on Nov 03, 2016
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 2
Next »
Date
2016-11-03
Attendees
Voting
Non-Voting
Discussion Items
Time | Item | Who | Notes |
---|
10 mins | | Former user (Deleted) | Meeting was quorate |
25 min | | Former user (Deleted) | - 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
| | |
---|
September 19 | Close of business (Pacific) deadline for feedback on spec draft including examples and feedback from implementers. | |
September 22 | WG call to review CR draft structure | |
September 29 | WG call to review CR draft and discuss items needing resolution | |
October 6 | WG call | |
October 13 | WG call | |
October 20 | Candidate draft to WG.
Decision required if the draft is sufficiently mature to base an IIW session on it. | |
October 27 | Final working session for WG (with/without IIW comments) on candidate draft | |
November 3 | Final draft for WG review | |
November 10 | Working group ballot - must be approved by WG on Nov 10th | |
November 15 | Send doc to the Leadership Council. They must approve it by Nov 30. | |
November 30 | LC Approval decision | |
December 1 | Kantara all member ballot begins. | |
January 15 2017 | Earliest Spec approval date | |