From 8fbb66fcf402d0f44bb4009289c34d1d97d5e6f8 Mon Sep 17 00:00:00 2001 From: Scott Kay Date: Thu, 18 Jan 2024 09:46:52 -0500 Subject: [PATCH] Update Consent String Specification.md --- Core/Consent String Specification.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/Core/Consent String Specification.md b/Core/Consent String Specification.md index 014ab83..3005ae8 100644 --- a/Core/Consent String Specification.md +++ b/Core/Consent String Specification.md @@ -199,9 +199,9 @@ The following details provide information on creating, storing, and managing a G
  • Concatenate all sections. Concatenate the encoded GPP header as the first item to the encoded versions of the discrete sections using “~” (tilde) as the delimiter. See examples of GPP strings below.
    • -Note that neither the header nor the recommended encoding mechanism for a discrete section utilizes base64 encoding but rather a modified version of it. +Note that the header and the recommended encoding algorithm for discrete sections utilize a modified version of base64 url safe encoding which omits byte alignment. This modification adapts base64 byte encoding to GPP bit encoding. For example, the GPP header `DBABM` decodes to the 30 bit sequence `000011000001000000000001001100` but cannot be decoded with the standard base64 algorithm. -#### Table from RFC 4648 +#### Base 64 URL Encoding Table from RFC 4648
    @@ -333,7 +333,7 @@ Note that neither the header nor the recommended encoding mechanism for a discre - + @@ -343,7 +343,7 @@ Note that neither the header nor the recommended encoding mechanism for a discre - + @@ -362,8 +362,8 @@ Note that neither the header nor the recommended encoding mechanism for a discre - - + +
    45 t 62+-
    1246 u 63/_
    13f 48 w(pad)=
    15