Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Date

Apr 11, 2016

Attendees

Agenda

  • Budget Update: Budget Awarded
  • Budget Breakdown:
    • Budget item - website + Hosting £600 (two options)
      • take existing website, host the domain by itself at godaddy for 3 years and put a video and guidance out on this website
      • alternative,  is keep hosted where it is, create a nice front page £100 -£150 - lets develop some articles and content, a white paper for  the website, and then maybe move it to github for £300 and leave it there with no hosting
    • Budget item - short video 
      • 30 sec - video to demonstrate what a consent receipt is
    • budget item - Design of website front page £100 +
    • £600 for travel in EU to EIC and Paris to represent Kantara CIS - (** item to OCG )
    • Real Consent - Workshop Sponsorship - £300 an event to Open Consent Group - Sponsorship partnership with PDTN - inlcude series  of 4 workshops, plus promotion of Kantara and the CIS WG in the UK/EU.

Editor Updates - 10 min

  v0.8 v1 draft Edit Review Update
After and during the call we talked about the next steps for the work focus and the result this week is a plan being proposed is to provide the MVCR as a normalised consent receipt profile for Networked Consent.    With the v0.8 specification featuring this normalised MVCR conformance profile.  

We are also looking at a more marketable name.  Perhaps something like the Networked Consent Receipt or Digital Consent Receipt (or the less accurate  Consent Receipt).  The MVCR phrase has been more about the process that is used to make a consent receipt, which is what the specification is about.   The MVCR normalised profile can have a much better name, as its about consent communication, so the name should reflect this.   (all name ideas or comments welcome)

Talked with Heather, and she is not available to edit until May, but will help if she can.

Vote

—> The Editors action item being to vote on the call Monday  to further define  a minimum viable consent receipt conformance profile for digital (and cross domain) consent.  Or the ’Network Consent - MVCR Profile'   ;-)  

—>  vote on tabling the MVCR Explicit and MVCR Compliant conformance profiles post v0.8 Draft (for as long as a v1.1 or v.1.2) depending on resources and interest.

—> Update on Real Consent - We have done a lot of work with two workshops delving into Real Consent, with another Real Consent Workshop planned for May 27th.  An update on this due Monday.

Some of the juicy core Marketing/CR outputs were:
a)  Consent Communication: ( or Consistent Open Consent) The MVCR - for online consent receipts (provides proof of consent) (see the requirements for the MVCR conformance profile)
b) Dynamic Consent - changing consent preferences after consent provided (or turning on and off permissions for secondary purpose)
c)  Consent By Design - marketing focused considerations  - see Real Consent & Design materials, if we could put some thought into the benefits you want to promote as a WG this would helps. .

Discussion Items

TimeItemWhoNotes
    

Action Items

  •  
  • No labels