This page represents the proposed structure of the ToIP Governance Metamodel. The purpose of the metamodel is to provide an overall template for ToIP-compatible governance frameworks from which the GSWG will then develop layer-specific templates. Each layer-specific template will be an instance of the metamodel that adds details such as:

• Standard ToIP Roles at that layer (see the GSWG Process and Roles TF)
• Standard ToIP Processes in which actors in those roles are engaged (see the GSWG Process and Roles TF)
• Recommended Policies for those Processes (see the GSWG Process and Roles TF)
• Standard Risks against which Risk Assessment should be performed (see the GSWG Trust Assurance TF)
• Standard elements of a Trust Assurance Framework to address those risks (see the GSWG Trust Assurance TF)

The balance of this page is an outline of the proposed metamodel. 

All terms appearing in First Letter Caps on this page MUST be added to the ToIP Glossary tagged for inclusion in the ToIP Governance Glossary. (Note: the Concepts and Terminology WG has already been briefed on this dependency.)

Master Document

The Master Document is the "home page" for the governance framework (GF). It:

1. MUST have a DID (Decentralized Identifier) that serves as an identifier of the entire GF.
2. MUST have a unique DID URL (defined in the DID spec) to identify each specific version of the Master Document.
3. MUST contain authoritative references to all other documents included in the GF, called the Controlled Documents.
4. MUST include policies stating how the Controlled Documents are governed by the Governance Authority.

Introduction

This section is a non-normative general introduction to the GF that orient first-time readers as to the overall context of the GF. It:

1. SHOULD have a reference to the ToIP Foundation, the ToIP Stack, and the ToIP Governance Template from which it was derived.
2. MAY include an Acknowledgements section to acknowledge the contributors to the GF.

Purpose

This is a short, clear statement of the purpose of the GF. It:

1. SHOULD be as short and concise as possible—ideally one sentence, or only a few sentences.

Scope

This is a statement of the scope of the Trust Community for which the GF is intended to provide governance. It:

1. SHOULD clearly state the stakeholders in the Trust Community.
2. SHOULD clearly state the high-level assets/artifacts (e.g. verifiable credentials, transactions, records) under oversight by the GF
3. SHOULD clearly state the overall shared trust objectives.
4. SHOULD, if applicable, clearly state who and what are out of scope.

Principles

This section states the Principles by which all members of the Trust Community have agreed to abide. It:

1. SHOULD serve as a guide to the development of any Policies based on each Principle ("Principles guide Policies").
2. SHOULD refer to existing Principles—whether defined by ToIP-Compatible GFs or by other bodies—whenever possible.
3. SHOULD NOT include language which conformance could be tested — those statements should be included as Policies.

Core Policies

This section contains the Policies that apply generally across the entire GF. It:

1. MUST include a Policy clearly explaining Governance of the GF—specifically how any revisions to the GF are developed and approved.
2. SHOULD include requirements that apply generally to governance of the entire Trust Community and that guide the development of more specific policies within the Controlled Documents.
3. SHOULD NOT include any requirements that apply in a specific context addressed by one of the Controlled Documents.
4. SHOULD be listed within categories making it helpful to understanding their context and intent.

Governance

The Governance section covers how the GF is governed. It:

1. MUST state the full legal identity and contact information for the Governance Authority.
2. MUST refer to a Core Policy clearly explaining Governance of the GF—specifically how any revisions to the GF are developed and approved.
3. MUST include references to any separate Controlled Documents that constitute Governance documents for the Governance Authority (e.g., Charter, Bylaws, Operating Rules, etc.)
4. SHOULD explain if there are interdependent Governance Authorities and provide a reference to an authoritative listing of such Governance Authorities and their responsibilities.

Schedule of Controlled Documents

This is a listing of all Controlled Documents. It:

1. MUST include authoritative references to all Controlled Documents in the GF.
2. MUST identify each Controlled Document with a unique, permanent DID or DID URL.
3. SHOULD include a Web link to each Controlled Document in the Web version of the GF.
4. SHOULD include a brief description of the purpose and scope of each Controlled Document to make it easy for readers to navigate the GF.

Controlled Documents

Each Controlled Document covers a specific specialized area of the GF. Each of the following are categories of Controlled Documents where each category MAY include zero or more Controlled Documents.

Glossary

The Glossary provides a common basis for terminology. It:

1. SHOULD be a single Controlled Document.
2. SHOULD provide a common reference for all terms used throughout the GF.
3. SHOULD reference the ToIP Glossary—or a tagged subset of the ToIP Glossary—for all terms defined there.
4. SHOULD list all terms alphabetically (by language) for easy reference.
5. MAY tag terms by category or usage.
6. MAY specify that terms specific to one Controlled Document be defined in that Controlled Document.

Risk Assessment, Trust Assurance, and Certification

This category includes policies for managing risk, including how parties can be certified against the GF. Controlled Documents in this category:

1. SHOULD identify key risks that MAY negatively affect the achievement of the GF's purpose within its scope
2. SHOULD include a Risk Assessment process output that provides an assessment of each key risk that the GF is designed to address and mitigate.
3. SHOULD assess which Roles and Processes are vulnerable to each risk and how they are affected.
4. SHOULD include a Risk Treatment Plan (RTP) for how identified risks are treated (e.g. mitigated, avoided, accepted or transferred).
5. SHOULD include a Trust Assurance Framework that defines how Roles MUST assert compliance with the Policies of the GF and the mechanisms of assurance over those assertions.
6. SHOULD (if applicable) define the roles of Auditors and Auditor Accreditors and the policies governing their actions.
7. SHOULD (if applicable) define the roles of Certification Authorities and the Policies governing their actions and relationships with the Governance Authority, Auditors, and Auditor Accreditors.

Governance Rules

These are the Rules for governing the GF as a whole. Controlled Documents in this category:

1. MUST specify all interdependent Governance Authorities (if any).
2. MUST include Controlled Documents that constitute:
   1. Governance Authority operations (e.g., Charter, Bylaws, Operating Rules, etc.)
   2. Each interdependent Governance Authority (e.g., Charter, Rules of Order, etc.)
3. MUST refer to the Core Policy and (if applicable) detail sub Policies under which Governance Framework documents can be revised.
4. SHOULD clearly state how such documents work together to define Governance for all components of the GF.

Business Rules

These are the Rules governing the business model(s) of the GF. Controlled Documents in this category:

1. SHOULD clearly explain the exchange(s) of value within the Trust Community that the GF is design to enable.
2. SHOULD define the Policies governing how and when these exchanges of value take place.
3. SHOULD define how all Members are accountable for their actions in these exchanges.
4. SHOULD define how the Governance Authority and the GF are sustainable under these Rules.

Technical Rules

These are the Rules governing technical interoperability. Controlled Documents in this category:

1. MUST specify how Members of the Trust Community will technically interoperate using the ToIP Stack by reference to ToIP Standard Specifications (TSS).
2. SHOULD (if necessary) reference one or more specific ToIP Interoperability Profiles (TIPs).
3. SHOULD specify any technical Policies or Specifications that are specific to this Trust Community.

Information Trust Rules

These are the Rules governing information security, privacy, availability, confidentiality and processing integrity. Controlled Documents in this category:

1. MUST specify how Members of the Trust Community will ensure information security by reference to:
   1. ToIP Standard Specifications (TSS).
   2. Other regulatory or industry standards.
   3. GF-specific Policies.
   4. Member-specific Policies.
2. MUST specify how Members of the Trust Community will ensure information privacy by reference to:
   1. ToIP Standard Specifications (TSS).
   2. Other regulatory or industry standards.
   3. GF-specific Policies.
   4. Member-specific Policies.
3. SHOULD specify how Members of the Trust Community will ensure information availability by reference to:
   1. ToIP Standard Specifications (TSS).
   2. Other regulatory or industry standards.
   3. GF-specific Policies.
   4. Member-specific Policies.
4. SHOULD specify how Members of the Trust Community will ensure information confidentiality by reference to:
   1. ToIP Standard Specifications (TSS).
   2. Other regulatory or industry standards.
   3. GF-specific Policies.
   4. Member-specific Policies.
5. SHOULD specify how Members of the Trust Community will ensure information processing integrity by reference to:
   1. ToIP Standard Specifications (TSS).
   2. Other regulatory or industry standards.
   3. GF-specific Policies.
   4. Member-specific Policies.

Inclusion, Equitability, and Accessibility Rules

These are the Rules governing inclusion, equitability and accessibility. Controlled Documents in this category:

1. MUST specify how Members of the Trust Community will enable and promote inclusion and equitability by reference to:
   1. ToIP Standard Specifications (TSS).
   2. Other regulatory or industry standards/guidelines.
   3. GF-specific Policies.
   4. Member-specific Policies.
2. MUST specify how Members of the Trust Community enable and promote accessibility by reference to:
   1. ToIP Standard Specifications (TSS).
   2. Other regulatory or industry standards.
   3. GF-specific Policies.
   4. Member-specific Policies.

Legal Agreements

This category include any legal agreements or contracts included in the GF. Controlled Documents in this category:

1. MUST include all legal agreements or contracts between Members of the GF and/or the Governance Authority.
2. SHOULD reference the Glossary document for all terms not defined within.
3. MUST clearly state the parties to which these legal agreements apply.
4. MUST define or reference the accountability and enforcement mechanisms.
5. MUST reference any other relevant Policies in the GF.