2017-01-12 Meeting Notes (CR)

10 mins

• Roll call

• Agenda bashing

• Meeting minutes approval

@Former user (Deleted)

• Prior minutes requiring approval

  • 2017-01-05 Meeting Notes (CR)

• "Move to approve listed meeting notes previously circulated"

  • Motion: Mark

  • Second: Iain

  • Discussion: None.

  • Result: Motion carried.

5 min

• Discussion on current version of CR

• Consent Receipt Specification wiki page

@Former user (Deleted)

• Public review and IPR claims period has started 2017-01-06, ends 2017-02-20

  • 1 comment to date

30 min

Discussion on what's next on the roadmap

All

New discussion 2016-01-12:

• Note that Virtual has collected ideas from CIS individuals on how to market CR

• Note EU Article 29 data portability - from Iain email

• from the GDPR -The GDPR is a consent based legal framework which specifies "a structured, commonly used, machine-readable and interoperable format” pg 15(68) GDPR

• Discussion about organization structures that would support the work and participation best

• Note that there is a good case to re-launch the Public Policy & Privacy & Legal WG - the pace of regulation changes is high right now

• Governance is missing from the mind map

  • Make sure this is in the charter of the top WG

  • The terms of reference must make roles and responsibilities clear for e.g. Project Managers

  • Make the case that projects can attract a different type of participant - the builders rather than the talkers

• By creating project teams we can assemble the required expertise regardless of which WG they come from

• Data Portability -> rename the Portable Data Exchange branch

  • discussion

    • PPP WG would have Data Portability in its remit

    • The Data Exchange for portability (protocols/specifications) would be in this sub-group

    • Portable data exchange - is mostly between data controllers rather than from the individual

Discussion from 2016-01-05:

• (From December 1, 2016 meeting)

• The list of subject areas that will be worked on:

  • Consent Receipt

    • There will be CR spec errata that will need to be fixed

    • A v1.1 will be required within 6 months after feedback from implementers

  • User Submitted Terms

    • Use case library and elaboration of use cases

    • UX design

    • Model contract language to support each feature of the UST elements

  • Requirements for API / Interfaces for CR and UST artifacts

  • Requirements (text) for implementers of Consent receipt generators (code)

  • Requirements (text) for Consent receipt 'viewer' (code)

  • Information Sharing Agreements

    • Architecture and model (text and diagrams)

    • Requirements (text)

      • Business requirements

        • Functional requirements

        • Non-functional requirements

    • Specifications (text)

  • Build a Kantara prototype implementation of a consent receipt management system

5 min

Discussion about changing the CIS WG structure after CR v1.0

@Former user (Deleted)