Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prefer "No Consent"/"Consent" to "Opted Out"/"Did Not Opt Out"? #95

Open
matt-martin opened this issue Sep 1, 2023 · 0 comments
Open

Comments

@matt-martin
Copy link

matt-martin commented Sep 1, 2023

In the specification, some fields define choices as:

0 Not Applicable

1 Opted Out

2 Did Not Opt Out

And in other places, the choices are defined as:

0 Not Applicable

1 No Consent

2 Consent 

The descriptions, "Opted Out" and "Did Not Opt Out", seem to make unnecessary assumptions about how the user expressed their consent or lack thereof (i.e. it seems to assume that the users are opted in by default and must explicitly opt out). This can get a bit confusing if another state passes a law in the future where this field is also applicable but all users are set to "No Consent" by default. Somebody casually reading through the spec may not realize that "Opted Out" is actually equivalent to "No Consent". I may be splitting hairs here, but it seems like it would be more consistent and less error prone to always refer to "Consent"/"No Consent".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant