-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Different JSON formats in different places #114
Comments
Hi,
That is an old consent receipt generator for version v0.09.
This is out of date now.
… On 24 Oct 2017, at 00:25, Shan Chathusanda Jayathilaka ***@***.***> wrote:
JSON format of your consent receipt specification v1.0.0 is much different from the JSON format in your Example Consent Receipt Generator ( mvcr.herokuapp.com ). So, what is the correct JSON format to deliver the consent receipt.
Thanks.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#114>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGPq5-nBiPdTQnD2TTY1y14F-VLYj7-Nks5svWbJgaJpZM4QD07T>.
|
Hi @smartopian , |
@ShanChathusanda93 Although the consent generator is not up-to-date, the latest version of the schema is at https://kantarainitiative.org/confluence/download/attachments/76447870/CR%20Schema%20v1_1_0%20DRAFT%205.json?version=1&modificationDate=1508987053000&api=v2 |
JSON format of your consent receipt specification v1.0.0 is much different from the JSON format in your Example Consent Receipt Generator ( mvcr.herokuapp.com ). So, what is the correct JSON format to deliver the consent receipt.
Thanks.
The text was updated successfully, but these errors were encountered: