Drivers do not resolve test vectors.

Most of the drivers do not resolve the test vectors out-of-the-box. On the DIF Universal Resolver site, only about 20-25% of the did methods are listed as "compliant". Several of the drivers that are listed are not registered on the W3C did-extensions repo.

I am sure the compliance issue is partly/mostly because the test vectors rely on infrastructure which is no longer running. For example, did:web reports errors, though it is an important method. But this is because the test vectors (such as did:web:did.actor:Bob) do not resolve due to did.actor apparently no longer being a valid domain name. There is nothing wrong with the did:web driver, I believe, and it resolves other did:web URIs, just not the test vectors. This is probably a typical reason for drivers indicated as "non-compliant".

To be honest, this makes the DIF Universal Resolver seem dead, and it does not reflect well on the state of DIDs overall. I don't like to ask, but is the DIF Universal Resolver in fact dead? If not, test vectors should be fixed, and drivers that are not "compliant" should be the exception, not the norm. After a grace period, drivers that cannot be reported as "compliant" should be disabled. An effort should be made to get more of the registered methods to provide drivers, and to remove drivers for methods which are not registered.