2015-05-18 Meeting Notes

Owned by Mark Lizar (Unlicensed)
Last updated: May 18, 2015
2 min read

Date

May 18, 2015

(To be posted online)

Attendees (voting)
* Mark Lizar
* Iain Henderson
* Heather Flanagan
* Mary Hodder
* Alexander Hanff

Attendees (non-voting)
* Oliver Maerz

Action item for the group:
Review the Work Book (see link below) because group must resolve what
fields go in the receipt.

Notes:
1. MVCR v0.7 update
See: https://github.com/KI-CISWG/MVCR

2. Website and the Demonstrator
Support for initial posting on Kantara site; note that we'll mostly get
'the converted' here, but hope/expect to be able to use the input to
expand to other, broader audiences

2. Consent Receipt Funding - Doing the Development - the plan in brief.

3. Technical Spec Meetings on Thursday
Expect calls on Thursdays as well to develop the technical
specifications (9pm GMT). Will be working on the JSON model.

4. Workbook - comments
This workbook is capturing the table that will need to go in the MVCR
"Consent Notice Fields and Descriptions" section
See:
https://docs.google.com/spreadsheets/d/1YcBz7tgnD8AOMYQ-NywfDSODyg2ArRu2FlYrkM3Ifuc/edit?usp=sharing

What goes in the actual receipt? See the "MVCR v0.7" page in the work
book "Fields".  See also list discussion, tracked in thread
<http://kantarainitiative.org/pipermail/wg-infosharing/2015-May/001266.html>
The CR shouldn't just cover what the user is knowingly giving the
provider; it should also cover what is going on behind the scenes (e.g.,
browser finger prints, IP numbers). Suggestion that the CR should cover
the metadata (classifications of data), instead of the entire list, to
help users make sense while minimizing info overload.
If we collect all the user data, we may have additional problems with
maintaining privacy.
The whole receipt will be made up of links and URLs. There will be URIs
to the receipts. The details shouldn't be in email to avoid profiling.
Remember the target of "Minimum Viable" - we need to collect and send as
little as possible.
If we have all the detail for the user, that allows for profiling; but
if we don't include the detail, then we lose the empowerment of users to
more easily know what's going on. We can follow up with the idea of all
detail, particularly in the site registration use case, but we should
keep the core CR spec should be kept as small as possible.

5. Process

6. Use Cases
See workbook

7.Roadmap
See original discussion: Roadmap thread
<http://kantarainitiative.org/pipermail/wg-infosharing/2015-February/001071.html>

a. finish v0.7 and create a receipt demonstrator
b. use this to create issues and develop v0.8
c. address issues and reflect in v0.9
d. put 0.9 out to Kantara Community for Review, collect all comments
e. V1 - Finish v1

AOB
Next full call scheduled for Monday, 25 May (note that is a major US
holiday, so participation may be light)
Next technical call scheduled for Thursday, 21 May

Â