Inconsistent example in Transparency & Consent Framework
deanWombourne opened this issue · 2 comments
In the example of a consent string on this page https://github.com/InteractiveAdvertisingBureau/GDPR-Transparency-and-Consent-Framework/blob/master/Consent%20string%20and%20vendor%20list%20formats%20v1.1%20Final.md#example-vendor-consent-string there is a breakdown of each field and it's bit value,
There is also those same bits joined together and split into byte groups (here https://github.com/InteractiveAdvertisingBureau/GDPR-Transparency-and-Consent-Framework/blob/master/Consent%20string%20and%20vendor%20list%20formats%20v1.1%20Final.md#concatenated-cookie-value-field-bits)
However, the byte groups and the original list of field values don't match - the bits grouped by byte has an extra zero byte on the end (i.e. the last two bytes are 00100000 00000000 but according to the earlier field breakdown the last 00000000 shouldn't be there).
The base64 encoded value is the base encoded original fields value without the extra byte on the end.
Why way should this inconsistency be corrected?
Yes the last 8 bits in he example below the table are incorrect
@deanWombourne Since September 2020, the TCF v1.1 is deprecated. Therefore, as this issue is related to this version, I close it.