trust_network
. For the roles to take effect, indexing
must be set to true
, otherwise the roles will not be stored by the indexer.roles
, you can describe what are the roles for your trust network, giving each of them a description
.issues
property. This can be used to create a hierarchy, where your node only creates an association to follow an authority.issues
property, you specify which roles can be issued, and what's the type of association for that role. In the example above, authority role can issue university role to an address when the association is type: 100
. issues
property is optional. When omitted, the role is an endpoint; it can't issue other roles.type
property does not mean the id of the role, but instead the association type. Different roles can issue differently based on the type
. This can be used to create more complex structures.type: 100
and type: 101
respectively. But authority issues the role of sub_authority when the association is type: 101
.authorization
property is an array of credential URLs that the role can issue. The framework is built on this property, which can then be used to verify the authority of a credential.authorization
should match JSON-LD URLs as used in the @context
property of the verifiable credential. Our example of university roles contains the context for college degrees: