...
| comment # | Line/Reference # | Proposed Change or Query | Proposer / Affiliation | Action / Decision (please leave blank) |
|---|---|---|---|---|
| 1 | 15 & elsewhere | I'm struggling to understand the use cases where there would be a "need" for personalization. Most of the time I hear about personalization to be a useability/user interface feature - we want to greet this individual by name once they have signed in. Would it be enough to say "I need my users to have a good experience, and personalizing their experience is a key component so I need these attributes"? I could even see an organization showing data that users respond better to being addressed by name. (a demonstration of the need?) I agree that a specific reason needs to be provided with specific information about how the attributes will be used. But, restricting this to "need" seems to me to be very much in the eyes of the beholder and a potential source of conflict. | Laura Paglione / SCG | |
| 2 | 29, 149, and elsewhere | Maybe I am not making the connection. Use of "personalized" seems like it could lead to confusion. The category is not a personalized attribute bundle, but is used to indicate a standard attribute bundle for personalization (line 122). Would suggest use of "personalization" (or something else) in the entity category definition instead of "personalized". | Mark Rank / Cirrus Identity | |
| 3 | ||||
| 4 | ||||
| 5 | ||||
| 6 | ||||
| 7 | ||||
| 8 |