Versions Compared

Old Version 2

changes.mady.by.user Former user (Deleted)

Saved on

compared with

New Version 3

changes.mady.by.user Former user (Deleted)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date

2018-08-16

...

  • Oscar Santolalla

Quorum Status


Meeting was <<>> not quorate


Voting participants

...

Time

Item

Who

Notes

4 mins
  • Roll call
  • Agenda bashing
Former user (Deleted)
  • Dev Team status
  • Sequence diagram and roles status
  • Storyboard status
  • Stage narrative status
  • Team issues and show stoppers
  • Dry run on Consent Management WG call Wednesday August 22 at 07:00 Pacific time
  • Andrew has set up a github repo for next-version specification backlog items: https://github.com/KantaraInitiative/consent-receipt-v-next
5 min
  • Organization updates
All

Please review these blogs offline for current status on Kantara and all the DG/WG:

There is a new wiki page that will hold all the known implementations of Consent Receipts - Please update the page or inform Andrew of your implementation.

Planning a Member Plenary meeting October 26-ish San Francisco (Friday after IIW)

  • Are there specific cross-group items you'd like to propose to work on?
40 minInteroperable Consent Receipt demo at MyData ConferenceAll

1) Dev team status

Google drive folder for export/import of consent receipts

  • digi.me
    • Discussing using the iOS Share button to invoke the JSON export
    • No code functionality will be available for the demo
    • Existing JSON file version
  • Consentua
    • WOOOOOO!!!!!!!
    • Code functionality is built and internet-available
    • Richard working on updating the SDK to expose this functionality
    • Will build a small demo app
  • Ubisecure
  • OpenConsent
  • Trunomi
    • Export code exists, but only on a dev laptop - customer demand has occupied all devs so no time to work on import function. We will get static screenshots and example receipt JSON files to show.
  • clym
    • Pulled out



2) Sequence diagram and roles status

  • Any questions?



3) Storyboard status




4) Stage narrative status

  • Andrew still has not started - but will have a dry run ready for next week on WEDNESDAY August 22 at 07:00 Pacific time



5) Team Issues and showstoppers discussion



AOB
  • digi.me marketing will be at MyData - a table doing rapid application development for health information - Rory Donelly (Global CEO), Tarik and Dan Bailey will be there

Next meeting

2018-08-23 same time, same number

GOAL IS TO HAVE ALL DEMO PARTICIPANTS JOIN THE CALL TO WORK OUT ANY MAJOR ISSUES

 

From 2018-08-02 call:

  • digi.me
  • Consentua
    • Still on track - deciding on timing of code change deployment on Monday - some front end work to go after that
  • Ubisecure
    • Still on track
  • OpenConsent
  • Trunomi
    • Still on track - JSON examples early next week
  • clym

From 2018-07-26 call:

  • digi.me
    • n/a
  • Consentua
    • Developers have promised CR output Week of August 6-10 - we will be looking for the output in the shared google folder (smile)
  • Ubisecure
    • n/a
  • OpenConsent
    • Viewer has been started - looking to get receipts from others
    • Target is August 15 to be able to display CRs
    • Open call to suggest features for OC to include - provide them this week if possible
  • Trunomi
    • currently in their 2-week dev sprint - target completion week of August 6-10
  • clym
    • n/a
  • Telus
    • Resource and scheduling estimates for creating an external CR for an existing app

AOB

  • Q: in the spec, Services is described as a 'business service'. But these days, companies are describing this as a 'category of business purposes'.
    • A: 'Service' is the name and description of the service - an unspecified field - mainly for humans
    • A: 'Purpose category' is to describe the business service purposes
    • A: If there is a Service with the same Purposes and the same Data as anonther Service, then they are indistinguishable.
  • Q: How are we envisioning asking the 'do you consent to this' question?
    • A: The Notice part of the flows have not been worked out yet in this group, deliberately.
  • Q: Have we decided on what format/location/interface will be recommended for the 'exported' CRs?
    • A: Right now, it's files in the Downloads folder (or a user-selected folder) - the 'real' discussion about this will be deferred until after the demo in August.
  • Q: How does COEL spec relate to the IETF secevent RFC?
  • mydata session - Joss
    • OneTrust, Nixu, JLINC, Kantara
    • Andrew asked for 20 minutes for the demo
    • Joss suggests that the Kantara demo goes last then transitions to Q&A for all
    • Q: Are there special provisions needed on the mydata web site to help people interact with the demo?
    • Need to focus the mydata demo presentation to trigger 'delivery' and action instead of 'interest'

From 2018-07-19 call:

...

  • new internal release v2.2 is available this week
  • some enhancements to Consent Access functions - some export functions
  • created field mapping versus specification - spreadsheet has been available for a few weeks
  • has new spreadsheet with updated JSON file info - has sent to David and Andrew for pre-review
  • digi.me has drafted a 'vendor extension' - proposal for new objects to be added to the spec
  • digi.me is done

...

  • Service is ready to go - just need to create a format for the CR spec - a configuration change, not a code change
  • work planned to start next week - planning session - will have more status on Monday

...

  • Minimal prototype - no CR in product
  • They will use the CR generator to create a sample app - a bookshop
  • CR will be downloadable

...

  • underway to create a Viewer plus Viewer API
  • scheduling estimates underway - target is to demo this at the interop demo

...

  • currently in their 2-week dev sprint - will have code after next week

...