Governments of Canada and the Pan Canadian Trust Framework

4 minute read

The Framework


  • Looking Ahead in 2020

    I believe it will be a breakout year for digital identity, and for the underlying technical infrastructure that we need to achieve our goals. I see the work progressing on two fronts: 1) Pan-Canadian Trust Framework, and, 2) Verifiable Credentials/Decentralized Identifiers Deployment.

  • Public Sector Profile of the Pan-Canadian Trust Framework Version 1.0 Recommendation Draft — Now available on GitHub

    The public sector profile of the PCTF reflects:

    • Evolution of the Identity Management Sub-Committee (IMSC) efforts.
    • The Need to Apply the PCTF for Assessments.
    • Policy Alignment.
  • IMSC Pan-Canadian Trust Framework Executive Summary

    This document describes Version 1.0 of the IMSC Pan-Canadian Trust Framework (PCTF). This framework is the next major step after the 2016 publication of the Pan-Canadian Trust Framework Overview by the Digital Identification and Authentication Council of Canada (DIACC), in collaboration with the Canadian public sector Identity Management Sub-Committee (IMSC) of the Joint Councils (JC).

  • IMSC Pan-Canadian Trust Framework - A summary of the latest iterations before our final version to be delivered on March 31st, 2019. The near to final document is here
  • The Pan-Canadian Trust Framework Using Prolog

    A ‘declarative framework’ (such as Prolog) focuses on the ‘what’ needs to be done, satisfied, relied on (i.e., proven to be true) versus ‘how to do it.’ In our case, with the Pan-Canadian Trust Framework (PCTF), it’s the question of ‘Can we rely on or accept a digital identity originating from a province or territory?’

  • Pan-Canadian Trust Framework - Tim Bouma

    The Pan-Canadian Trust Framework is how we will formalize the approval and acceptance of a “trusted digital identity.”

Annex E - 2014- 2017 Federating Identity: Milestones and Initiatives

Comments by Staticman and Identosphere

Leave a Comment

Your email address will not be published. Required fields are marked *