DID API

[decentralgabe]

Service shuffling. DID API support

[mistermoe]

the overall pattern makes sense to me. Naming is throwing me off a bit. Naming is always subjective and words are hard. Here’s my opinion though:

The VC Service contains services it seems. one of which will likely be a VC service. which makes things complicated to grok. Specifically this. I almost wonder if it’d make more sense if the VC Service was a collection of APIs (DID API, VC API etc.)

and I wonder if the VC Service should be called the SSI service. which exposes APIs like the VC API, DID API etc.

Super curious to hear your thoughts. This almost makes me wonder, if you're on board with SSI service, do we change did-sdk -> ssi-sdk 🤔

[decentralgabe]

the overall pattern makes sense to me. Naming is throwing me off a bit. Naming is always subjective and words are hard. Here’s my opinion though:

The VC Service contains services it seems. one of which will likely be a VC service. which makes things complicated to grok. Specifically this. I almost wonder if it’d make more sense if the VC Service was a collection of APIs (DID API, VC API etc.)

and I wonder if the VC Service should be called the SSI service. which exposes APIs like the VC API, DID API etc.

Super curious to hear your thoughts. This almost makes me wonder, if you're on board with SSI service, do we change did-sdk -> ssi-sdk 🤔

They should be consistent, I agree. The scope of the DID SDK is larger than DIDs, and the scope of the VC Service is larger than VCS. I agree with ssi-sdk and ssi-service; its less ambiguous than "DID" meaning "decentralized identity" over "decentralized identifiers".

[decentralgabe]

will handle renaming now, tests in the next PR