diff --git a/Core/Consent String Specification.md b/Core/Consent String Specification.md index bad5e9f..c999335 100644 --- a/Core/Consent String Specification.md +++ b/Core/Consent String Specification.md @@ -174,9 +174,9 @@ To decode a code word, remove the final "1", assign the remaining values 1,2,3,5 The following details provide information on creating, storing, and managing a GPP String. The basic steps for creating a GPP String are as follows: 1. **Create discrete sections.** For each section: - - For sections that use the recommended base64-websafe encoding, create a bit representation of the section’s header (if it exists) and each sub-section. Then, convert them to base64-websafe without padding (i.e. removing “=” at the end) and concatenate the header and all sub-sections using the “.” (dot) character. + - For sections that use the recommended base64-websafe encoding, create a bit representation of the section’s header (if it exists) and each sub-section adding padding (0) on the right to get to a multiple of 6. Then, convert them to base64-websafe without padding (i.e. removing “=” at the end) and concatenate the header and all sub-sections using the “.” (dot) character. - For sections that use different encoding, ensure that the data is websafe and does not include the “~” (tilde) character. -2. **Create header section.** Create a bit representation of the GPP header section. Include all IDs for discrete sections in a sorted order. Then, convert it to base64-websafe without padding. +2. **Create header section.** Create a bit representation of the GPP header section. Include all IDs for discrete sections in a sorted order. Add padding (0) on the right to get to a multiple of 6. Then, convert it to base64-websafe without padding. 3. **Concatenate all sections.** Concatenate the GPP-header as the first item to the encoded versions of the discrete sections using “~” (tilde) as the delimiter. @@ -266,10 +266,10 @@ The Header is always required and always comes first. It consists of the followi Based on the Section ID table above, the Section ID for EU TCF v2 is 2. - Full header bit string: 000011 000001 000000000001 0 011 + Full header bit string with padding: 000011 000001 000000 000001 001100 - Encoded header: DBABMA + Encoded header: DBABM @@ -298,7 +298,7 @@ Based on the Section ID table above, the Section ID for EU TCF v2 is 2.
  • Version = 000001
  • Section Range