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

PostMessage/SendMessage version example clarification #88

Open
janwinkler opened this issue Jul 9, 2023 · 1 comment
Open

PostMessage/SendMessage version example clarification #88

janwinkler opened this issue Jul 9, 2023 · 1 comment

Comments

@janwinkler
Copy link

The example under Sent Message (https://github.com/InteractiveAdvertisingBureau/Global-Privacy-Platform/blob/main/Core/CMP%20API%20Specification.md#sent-message) includes a property "version" which implies that the vendor can tell the CMP which gpp version to use. In all other commands we always assumed that the vendor will call the command and receive a response containing the gpp version. We need clarification on what is the expected behavior. e.g. if the CMP supports version 1.1 (and no longer 1.0) but the vendor sends

  __gppCall: {
    command: 'command',
    parameter: 'parameter,
    **version: '1.0',**
    callId: 'randomID'
  }
}

Shall the CMP reject the call. treat it as 1.1 or is the CMP expected to support both versions?

@janwinkler
Copy link
Author

Correction: The __gpp function also includes a version property (was this always there?), hence the same question applies for all command calls: What should the CMP do if a non-supported version is requested?

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