# Description: This functionality MUST validate the output of the trust discovery functionality of the Trusted Content Resolver. The validation functionality MUST validate the association of DID with a well- known DID configuration. Then it MUST also be able to validate the issuer details from the trust lists extracted from service endpoints. ## To be discussed: @mzigldrum @dsukhoroslov @schulzesttsi And MUST also be able to validate the integrity of the VC. -> Maybe this is part of client and not TCR backend. # Interfaces: - TCR Trust Discovery - Well known DID Config # Dependencies: - #9 - Universal Resolver - Well Known DID config # Acceptance Criteria: - *VC validation mechanism supports multiple signature proofs* TBD. - OCI compliant containerization (Dockerized) - Resolve different trust strategies - Resolve multiple lists - Implement the resolving strategies - Routes are documented through Openapi