| | | |
|---|
4 mins | | @Former user (Deleted) | Please remember to update your entry on the Consent Receipts Implementations Page - this is a major landing point for external viewers and raises awareness of the CIS WG work and your product too Update on Charter refresh work AOB Discuss next steps for receipt specification
|
10 min | | All | Please review these blogs offline for current status on Kantara and all the DG/WG: There is a wiki page that will hold all the known implementations of Consent Receipts - Please update the page or inform Jim, or John, or Andrew of your implementation. |
5 min | News about new implementations | All | This is a new standing agenda item where we can hear about new implementations of receipts. Jan Lindquist (Dativa) has created a Hyperledger Indy system that includes data sharing receipts using either identified or anonymous proofs of consent. This is kinda groundbreaking work and is a very interesting contrast to other ways of perceiving the role of 'proof' in the system. MOTION: Secretary to schedule a time on a future call for Jan to demonstrate the prototype. Moved: Jim Second: Lisa Discussion: None Motion carried MOTION: To schedule a presentation from Harsh on the W3C Data Privacy Vocabulary community group report - on July 18 2019 call. Moved: Mark Second: Lisa Discussion: Relevance and importance to the work of this group is clear - good opportunity to learn. Motion carried
|
15 min | Processing feature requests for v.next specification work | Jim | The WG should jointly work on a reference use case to frame up the discussions for next specification enhancement There are other known projects that are dependent on the Kantara specification but this WG does not have a listing of these impacted projects. This list might be well suited to be added to the 'implementations' page. ACTION: Mark to create a list of projects that rely on the Kantara Consent Receipt Specification v1.1 who need to be aware of changes to the Kantara specification. There is an existing backlog of features and bugs left over from v1.1 that need to be addressed MOTION: Move that open issues from V1.1 be moved to V-Next to be dealt with by the WG. Moved: John Second: Jim Discussion: Counterproposal - to work on incorporating the fixes from the outstanding v1.1 items into the current v1.1 spec then taking the remainder forward into v.next Issue is that any changes need to be resolved by the WG Concern raised that new use cases will displace current use cases Mark requests that a call time is reserved to discuss outstanding v1.1 items The result of processing of the v1.1 items could a) be simple bugfixes; b) result in a v1.2; c) impact future specification releases and should be incorporated into the roadmap. John proposes: Suggest the following for next week's agenda: Reviewing the list and identifying items to be a)discarded/deprecated, b) minor typo/bug/cleanup for 1.1a, c) amendments to 1.2 in line with intent of 1.1 charter and d) roadmap items to be folded into next major release (mapping to the new charter).
Motion deferred - quorum was lost - to be concluded on next week's call.
|
0 min | Specification enhancement project status | Jim |
|
|
|
|
|
0 min | Demo status update | all | Recording from Identiverse should be available by end of July. The presentation is now modular with short videos available to show implementations in Kantara Members' products. |
0 min | Specification update approach |
| See a flowchart version of this here: https://share.mindmanager.com/#publish/b-DWOcuKGnVY1PXBKXTpL0-DQOeqmZMGfGUAPiC5 |
20 min | WG Charter Refresh | Iain Henderson | |
5 min | AOB |
| |
| Next meeting |
| *** Next call 2019-07-18 10:30 am Eastern DAYLIGHT Time https://global.gotomeeting.com/join/323930725 John moves adjournment; Mark seconds. Meeting adjourned
|