2015-06-04 Meeting Notes

Date

Jun 04, 2015

We discussed the MVCR Use case for consentreceipts.org
- use core model and its viewable in a browser with javascript
- downloadable as jwt, jwt provides the option for it to be signed. Body of the consent receipt is json, but the container is signable
APi, takes in all the different fields - checks them for appropriateness of value
generates a signed consent receipt object jwt
on top of this - would be a very simple javascript website, has tools enable people to fill out the form and give a visual of the receipt
all this javascript does is call the api,
Implementation Options
- run your own consent server
- third party provisioning
plan would be to develop consent receipt generator on consentreceipt.org, Justin would do application design, and a bit of engineering, and Sarah, would do some UX and the web development, oliver would implement on Kantara website, would develop a client application to do on consent receipt.org
click on the join kantara, - go over to consent receipts,org and it would return the jwt.
- how do we get that button into the right place, can he manage that implementation?
- call the api on consent receipts .org.
the upgraded consent button - the button sets the fields needed --. s a dynamic web api – the kantara buttong
- re-useable - render code, so that it cut and pasted on Kantara website.
Consent Receipt.org needs open source with liberal license

Issues to add to list

who is legally allowed to issue a consent receipt for
- this is designated:
  - this would be under contract, to provide consent receipts and would need terms and policies.
  - this would have a consent provisioning contract, which is mixing, a contract,

- review/finalise the fields for the MVCR

- discuss/develop th consent receipt generator with a common data model so we can play with the model,

- continue the structuring of the data model

- discuss next steps (if we get this far)

Time	Item	Who	Notes