2015-06-25 CR-Tech Meeting Notes

Date

Jun 25, 2015

Attendees

Goals

  • Discussing the next steps
  • github.com/bspk/mvcr
    • create documentation for the API,
  • action: Justin & Sarah writing up initial documentation for v.07 spec,
    • this will include : Name field, name what field consists and what is currently validated - i.e. -
  • Action: Oliver - work on  CR Kantara implementation for CISWG
    • Kantara to store in the back end in the form add text - "we have created a consent receipt - email us if you would like a copy in the future
    • Oliver is going to make the button and call the API and we will play with it over the next week

Plan going forward

  •  We work through the format logic, and validation, these, create comments and notes where needed, and list issues (and when issues should be addressed)
  • keeping this in Consent Receipt v0.7 Issues & Generator Comments
  • Note: Format and validation should in most cases  by approved by the group for v.09
  • i.e. - we took first field Jurisdiction as an ISO - two country character code, needs second field for state/province,(may have rules per jurisdiction) 
    • validation may mean - checking that this company is in that country
  • We discussed mapping different objects - i.e. jurisdiction to ISO two character country codes.  This is important so that on aggregate, we can have a consistent and perhaps singular view.

    • Justin mentioned that we can also have it a bit more free style and that these would become more structure mapping over time.  Its clear that multiple strategies may come into play here.

       

       

Â