[IDM.TRAIN.00016] Trusted Content Resolver - Trust Discovery
Description:
This functionality MUST allow for the resolution of the trust list to find the issuer details in the trust list.
The resolver MUST base on the DIF Universal Resolver and MUST provide additional functionality to iterate recursive over DID Documents by resolving references in service endpoints during the standard resolving.
The resolving MUST be controllable by giving a list of endpoint types which are considered during the resolving by a defined range of actions.
Responding content references MUST be collected and provided to the user either as list or as Callback during/after the resolving of standard documents. For instance, when a DID is resolved, the extended universal resolver collects additional DIDs from the service endpoint section (selected by types) and searches there again for other content.
During this process, the defined content types are collected as reference. E.g., a list of URLs to type “gx-trusted-issuer” grouped by DID for a later processing by the libraries.
Interfaces
- DNS
- Universal Resolver
- IPFS/REST
Input
- Trust Framework Pointer (e.g., example.federation1.de) + Types to be considered
- ServiceType of the trust list (e.g., issuance service, verifier service)
Output - Not yet certain.
- Corresponding DID mapped to Trust Framework Pointer
- DID Document of the DID
- Trust List VC endpoint
Acceptance Criteria:
See Description and below:
- Use standardized DNS resolvers
- Use standardized DID resolver
- Navigate multiple trust framework pointers
- Discover different trust list formats
- Support different service types
- Optimized search mechanisms (e.g., Merkle Tree)
- MUST Allow configuration of different DNS Name Servers
- MUST allow configuration of user defined service content type (e.g., gxfs-trusted-issuer)
- REST Routes MUST be documented via OpenAPI