You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note that even if one may desire to remain anonymous when purchasing alcohol, a photo ID may still be required to provide appropriate assurance to the merchant. The merchant may not need to know your name or other details (other than that you are over a certain age), but in many cases a mere proof of age may still be insufficient to meet regulations. We need to mention language in the specification calling this out specifically.
The text was updated successfully, but these errors were encountered:
msporny
added
editorial
Purely editorial changes to the specification.
privacy-tracker
Group bringing to attention of Privacy, or tracked by the Privacy Group but not needing response.
labels
Nov 28, 2016
I always considered this use case to be somewhat abstract. Of course a "isOverAge": 21 is not yet compatible with regulations that say "Only a DMV, military or government photo ID is accepted as proof of age". Those regulations weren't developed until after the technology to print photo IDs was widely deployed. It seems like the default would be to assume the same thing would happen with proof of age credentials, that they would only be accepted by governments after they are widely deployed for use in less regulation-impacted commercial transactions, like offers/coupons/loyalty programs.
To my eye, no addition is necessary to support this request, but modifying the use cases to call it out wouldn't detract from the document, so I'm neutral as to whether to make a change.
Note that even if one may desire to remain anonymous when purchasing alcohol, a photo ID may still be required to provide appropriate assurance to the merchant. The merchant may not need to know your name or other details (other than that you are over a certain age), but in many cases a mere proof of age may still be insufficient to meet regulations. We need to mention language in the specification calling this out specifically.
The text was updated successfully, but these errors were encountered: