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

Clarification on unsupported APIs needed #4

Open
janwinkler opened this issue Oct 11, 2022 · 0 comments
Open

Clarification on unsupported APIs needed #4

janwinkler opened this issue Oct 11, 2022 · 0 comments

Comments

@janwinkler
Copy link

A clarification is needed what a CMP should do when receiving a consent string that includes an unsupported section. The CMP might not be able to decode it but is required to encode it (concat it to the full consent string).

Suggested wording:
When a CMP finds a section in a consent string that is encoded in a format that is not supported by the CMP, the CMP is required to store this section. When creating or updating the consent string, the CMP is required to include the original section in the new or updated consent string.

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