I'm high jacking this issue instead of opening a new one relating to the discussion thread on #629

There's concern about what/how interoperability components should be tested.

@nissimsan could you expand on your checklist? Outdated in relation to what? Am I to understand we want to remove all conformance testing from the test-suites? Which endpoints are we looking to trim and what does this mean?

There was a point made from @OR13 to only test the essential. Could we list what is to be considered essential testing?

Looking at the specification, these are the required features to implement:

• Data model (1.1 -> 2.0)
• Ed25519Signature2018
• DID WEB
• StatusList (StatusList2021 -> BitstringStatusList)
• Oauth presentation exchanges

If I was to draft an essentials list of tests based on these, I would include:

• Web did resolving
• OAuth token requests
• Data model testing for issued VC's
• Cross implementation VC verification, including status updates

AFAIK, the latest requirements are:

1. JWT with ES256 based on VCDM v2
2. OAuth Presentation Endpoint

Internally, a vendor will need to support:

• Schemas from Trace Vocab
• Bitstring Status List
• DID Web Resolution for arbitrary websites

A vendor might find it also helpful to implement, but we should not be required to maintain tests for:

1. VCDM v2 JWT Issuance, Verify and Present
2. Status List GET and UPDATE
3. DID Web Resolver

We should remove conformance tests from repo and from spec.

Remove sentence referencing did auth as outlined here: #604 (comment)