Expected content for Kantara fork of ConsentReceipt.org GitHub developer page

[dazzaji]

1. explains the Consent Receipt Specification and its dev
2. Shows the common format,
3. shows the api & api document page
4. shows the guides and new work
5. with CIS workgroup branding
6. form asks for feedback on specification, links to CIS workgroup wiki and creates the feedback loop needed to make next iteration of the specification and deploy it back out to the network in the specification part of the ‘ConsentReceipt’ repository

[dazzaji]

Item 2 above "Shows the common format" means that it should be clear that the "minimum viable" consent receipt is expected to have a minimum number of field in a particular order. The fields in the proper order are listed in the API doc. The required subset should be 1-4, including:

Section 1:
CR Header

Section 2:
Data Controller

Section 3:
Purpose Specification

Section 4:
Sensitive Personal Information

The documentation also includes additional fields which are not currently considered required/mandatory,

Section 5:
Information Sharing

Section 6:
Optional Or In Review

[dazzaji]

Mark will update the documentation accordingly.

[dazzaji]

Also, item 1 has already been done by Mark as follows:

Welcome to the MVCR,(Minimum Viable Consent Receipt) specification and demonstration api on GitHub. This api uses the MVCR consent receipt specification from Kantara Consent & Information Sharing Work Group. The MVCR is currently being developed as an open all purpose consent record core field format. The aim is to prvide the minimum common field set for consent, so that this consent format can be common for all human readable consent records. The intention is for this MVCR to be used as a base record format for human understandable transaction records. The core functionality of the MVCR is the purpose, contact, and attribute information required for consent, to be used as a communication channel for consent management. In this version of the consent receipt specification and api there are some experimental components. The first is the addition of the Information Sharing section onto the core MVCR format. For the API this is an optional field and used to demonstrate how to use receipt data to ext4end the functionality, data risk and value of the receipt. Also in this version there are a test set of Personal Infomration attributes and Purposes in the drop down boxes of the demo API. These are for test and demonstration purposes only and not recommended or supported. These appear in the dropdown list of the api and can be found in the appendix of the (MVCR v0.7)[] draft of the specification. Any implementation at this time should use their own purpose, but may find these references handy. Current work effort status is v.07: Currently we are organising work­shops for; purpose and attributes. We will also be having a receipt design session, researching design requirements, with the ideas that purpose(s) can be represented by icons and the like.

[smartopian]

This task should read, - need to attribute Kantara and the WG who is developing and making this. Link to appropriate content.

I appreciate keeping this as a clean dev repository. but, need to add the appropriate links and attribute appropriately.
At a minimum

1. Needs to link to the api documentation first,
2. needs to indicate (and attribute) the core fields (MVCR) to keep the format

[dazzaji]

Logo for footer