...

The purpose of this TSS is to specify the standard requirements that apply to all ToIP-compatible governance frameworks (GF) regardless of their layer in the ToIP Stack. 

...

Motivations

The overall purpose of the ToIP Governance Stack is to enable users of the ToIP Technology Stack to make Transitive Trust decisions based on Governance Frameworks that are include both humanHuman-auditable Auditable and machineMachine-testableTestable Requirements. While Governance Frameworks can are expected to be specialized for all four layers of the ToIP Stack, certain requirements interoperability Requirements apply to all ToIP-Compliant Governance Frameworks regardless of layer. The goal of this specification is to specify all of those interoperability requirements in a single specificationone place. 

ToIP Governance

...

Metamodel TSS

The purpose of the ToIP ToIP Governance Metamodel is to provide an overall template for ToIPa separate specification of the overall requirements for the structure and content of all ToIP-Compliant Governance Frameworks from which the GSWG will then develop layer-specific templates.The ToIP Governance Metamodel is currently defined on its own wiki page. The contents of that page will be incorporated into this section of the . All ToIP-Compliant Governance Frameworks MUST conform to the ToIP Governance Metamodel TSS.

Identification Requirements

...

1. Governing Authority (GA)
2. Primary Document
3. All Participants fulfilling Roles defined in the GF (e.g., Issuers, Stewards, Member DirectoriesTrust Registries)

The following SHOULD have Public DID URLs compliant with the ToIP Technology Stack:

...

1. The GA MUST publish in its current DID Document a Digital Signature over the hash of the current version of its Primary Document.
2. The GA SHOULD issue VCs to all Participants verifying the GF role played by the Participant.
3. If the GA specifies certification policies, Certification Authorities SHOULD issue Certification VCs to Holders as directed by the GF.
4. The GA or Certification Authorities SHOULD consider publishing either or both:
   1. Certification VCs to a Credential Registry
   and/or a Member Directory
   1. .
   2. Role DIDs to a Trust Registry.

Transparency Requirements

...

1. MUST be published on the Web.
2. MUST publish its DID URL in its DID Document.
3. MUST publish its Public Keys in its DID Document.
4. MUST publish its Public Service Endpoints in its DID Document.

Equity, Accessibility, and Inclusion Requirements

To support Transitive Trust, a publicly-available ToIP-Compliant Governance Framework:

1. SHOULD be published in all human languages spoken within its Trust Community.
2. SHOULD be accessible under the W3C Accessibility Guidelines.
3. SHOULD include provisions for digital guardianship if applicable to its Trust Community.
4. SHOULD NOT discriminate against legitimate members of its Trust Community.

Technical Interoperability Requirements

...