2015-06-18 Meeting Notes

Date

Jun 18, 2015

Review of CR-Generator
- Comprised of an input form on the left hand side
  - everything is in a string - nothing checked and no formating
  - example text
- when click create - javasccript calls consent receipt api - - post them to the generator API
The grey box on the right side is not the receipt but a rendering of the receipt
when clicking download reciept it creates a sign json token
to see what is inside - goto jwt.io and past in the token- with the header of the body and the signature
JTI - s a rendered field
IAT - is time stamp
issuer - points to the service that actually created the receipt - so third party can sign the receipt.
Justin thinks that this is easy, and that the will want to make their own,
create a button that will call the api. and pass in the data fields. that have been set.
can send json fields directly to the API and it will send back a receipt.
all of the code is on github with an apache license

Next steps,

Add use cases to the receipt generator and review the receipt and process.
- https://github.com/bspk/mvcr/issues/new
Further define what goes into each of the fields
Further define how the field should act.
- validation - validate that the data sent to the API is what is expected. - validated at both sides
Add - issues to git hub.com issue function - for small issues
for bigger issues, i.e. fields and formats these should go to the list
once decided add them to the git hub tracker.

Sarah and Justin up for mechanical cleanups, (not new functionality - i.e. a data store or aggregate use )

Actions:

Mark Lizar (Unlicensed) review and send to list comments - add obvious issues into git hub tracker.