...
Number | Section, if applicable (overall comments also welcome) | Current Text if applicable (overall comments also welcome) | Proposed Text / Query / Suggestion | Proposer | +1 (add your name here if you agree with the proposal) |
|---|---|---|---|---|---|
| 1 | 9.3 in 63C | Data Minimization | Providing insufficient attributes may impact the functionality of the application. If the RP can identify which attributes are needed for which functions, it will help a user determine what to release. | Ken Klingenstein | |
| 2 | 9.3 in 63C | Data minimization for portals is particularly vexing. Guidance on how to do this would be helpful. | Ken Klingenstein | Brett Bieber | |
| 3 | 10.1.1 in 63C | Provide users means to delete their identities completely, removing all information about the user, to include transaction history. | There are often legal or audit reasons to not delete transaction histories. | Ken Klingenstein | Brett Bieber |
| 4 | 10.2.1 in 63C and 9 in 63A | Neither section appears to offer guidance on the translation of technical attribute names and values into user-friendly language. | Ken Klingenstein | ||
| 5 | |||||
| 6 | |||||
| 7 | |||||
| 8 |
See also