Versions Compared

Key

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

Roll

Mark Lizar

Salvatore D'Agostino

Gigi Agassini

Tim Lloyd

Quorate

IPR statement

acknowledged

Etiquette

  • Call etiquette,

    • start with listing updates -

      • Business of ANCR -

        • TPS scheme - TPS 1 - shpws valid consent market -

          • Action

Agenda

Updates

IEEE SC2 adopting/joining controller credential

IEEE Digital Privacy Initiative webcast, and also license adoption

NFID controller credential

SIA Biometrics best practice

Mailing list items

WG response, awareness of thread on ISO/IEC 29184:2020 Online privacy notices and consent, recommendation to make this open and free.

Passed by unanimous vote.

Motion to pass recommendation to LC.

Making 27560 free, as recommended at the last ISO Manchester meeting, without 29184 means that the security and privacy controls for notices are not available for the consent record. The motion is to make 29184 open is driven by the need for people can use standards to manage their identifies and the related privacy and security list. This enables the use of the ANCR Transparency Performance Indicators and the associated developing framework and scheme as public digital transparency infrastructure that can be used by people, regulators, and organizations.

Actions

  •  Roadmap
    •  Confirm existing Roadmap
      •  TPI Doc
      •  Charter
      •  License Action
      •  Consensus specification
  •  Funding to do “the” work (Update all of ANCR specifications)
    •  Sources
      •  
      •  Kantara request for technical writer support.
    •  Time frame …
  •  Agenda template

Could the ANCR call advance from the standards and the ANCR specs to also introducing discussion of "reference architectures" and "Application Notes" and such - other treatments helping communicate standards and bridge to adoption streams?

Could the ANCR call advance from the standards and the ANCR specs to also introducing discussion of "reference architectures" and "Application Notes" and such - other treatments helping communicate standards and bridge to adoption streams? We seem to need to shift phase in a manner of speaking "cross the chasm" from abstract requirements to concrete implementation proving grounds and iterative refinement based on real world evidence.

Early integration to help broaden adoption.