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
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
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?
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
Shall the CMP reject the call. treat it as 1.1 or is the CMP expected to support both versions?
The text was updated successfully, but these errors were encountered: