Page History

...

1. The following MUST have public DIDs compliant with the ToIP Technology Technical Architecture Specification:
   1. Governing authorit(ies).
   2. Administering authority (if any).
   3. Primary document.
   4. All governed parties fulfilling roles defined in the GF (e.g., issuers, verifiers, trust registries).
2. The following SHOULD have public DIDs or DID URLs compliant with the ToIP Technology Technical Architecture Specification:
   1. Each controlled document.
   2. Each policy, rule or other normative subcomponent of a controlled document.
3. All DIDs and DID URLs specified in this section are subject to the following policies:
   1. The DID for a GF document MUST remain the same for all versions of the document it identifies.
   2. A new versionId parameter value MUST be assigned for every version of the identified document.
4. The GF MUST include one or more policies specifying the format for version identifier values and the process for assigning them.
   1. These policies SHOULD be the same for all versions of all documents in the GF.
   2. It is RECOMMENDED to use sequential integers for every version starting with "1".
   3. The use of minor version numbers (e.g., "1.1", "1.2", "1.3") is NOT RECOMMENDED.
5. A DID URL that includes a resource parameter with a value of true MUST return the identified document directly.
   1. If this DID URL does not include a versionId parameter value, it MUST return the current version of the identified document
   2. If this DID URL includes a versionId parameter value, it MUST return the identified version of the identified document.
   3. If this DID URL includes a versionId parameter value for a version that does not exist, it MUST return a "Resource Not Found" error.

...

1. The governing authority SHOULD publish a digital signature in its current DID document a digital signature over  over the hash of the current version of its primary document.
2. The governing authority or administering authority SHOULD:
   1. Register the public DID and all authorized roles for a governed party in a trust registry.
   2. Issue verifiable credentials to all governed parties serving in a role defined by the GF.
   3. Issue Store those same verifiable credentials to  in a publicly-available credential registry as specified by the GF.
3. If the GF includes certification policies, the qualified certifying parties SHOULD:
   1. Issue certification credentials to governed parties as directed by the GF.
   2. Issue Store those same verifiable credentials to  in a publicly-available credential registry as specified by the GF.

...

To support the transparency needed for transitive trust, a publicly-available ToIP-compliant GF: 

1. MUST be published, addressible on the Webpublic Internet.
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.
5. SHOULD be translated localized into all human languages spoken within as required by its trust community.
6. SHOULD be accessible under the W3C Accessibility Guidelines.

...

To support the interoperability needed for transitive trust, a publicly-available ToIP-compliant GF:

1. MUST specify technical interoperability interoperability requirements using ToIP specifications and recommendations whenever possible.
2. SHOULD specify any additional technical interoperability requirements using publicly available open standard specifications or specification profiles if needed.