diff --git a/Core/CMP API Specification.md b/Core/CMP API Specification.md index 94861dc..fadcebb 100644 --- a/Core/CMP API Specification.md +++ b/Core/CMP API Specification.md @@ -661,7 +661,7 @@ The key names are a combination of the “IABGPP_” prefix followed by the sect IABGPP_[SectionID]_String String - String representaiton of each section. E.g. IAB TCF EU v2 String will be found at IABGPP_TCFEU2_String + String representaiton of each section. E.g. IAB TCF EU v2 String will be found at IABGPP_2_String diff --git a/Core/Consent String Specification.md b/Core/Consent String Specification.md index 8b475ac..0e9211b 100644 --- a/Core/Consent String Specification.md +++ b/Core/Consent String Specification.md @@ -423,7 +423,7 @@ The possible data types are: String (fixed length of x) (including country codes) x*6 bit - A fixed amount of bit representing a string. The character’s ASCII integer ID is subtracted by 65 and encoded into an int(6).

Example: int(6) “101010” represents integer 47 + 65 = char “h” + A fixed amount of bit representing a string. The character’s ASCII integer ID is subtracted by 65 and encoded into an int(6).

Example: int(6) “101010” represents integer 42 + 65 = char “k” @@ -517,7 +517,7 @@ Note: items MUST be in sorted order..
  • First data type is an Integer (fixed length of 16 bit).
  • Second data type is always a Boolean.
  • If the second data type is 1/true, the third data type is an Int Range
  • -
  • If the second data type is 0/false, the second data type is a Variable length bitfield.
  • +
  • If the second data type is 0/false, the second data type is a bitfield of length determined by the first data type (see above)
  • Note: This data type is used for downwards compatibility only. OptimizedRange is the recommended data type to be used moving forward.