You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I understand the difference between VIDs and DIDs, but I think the term "VID method" isn't defined or explained anywhere. In the OpenAPI specs, there are the following endpoint and data structure:
But the description says it returns a list of DID methods. If there is no difference between VID methods and DID methods, then why use this term in the API specs? Or is the idea that in the future there could potentially be non-DID VID methods?
The text was updated successfully, but these errors were encountered:
peacekeeper
changed the title
Difference VID methods and DID methods?
Difference between VID methods and DID methods?
Oct 20, 2024
@peacekeeper, PR #73 migrates all VID methods to DID methods and keeps it consistent throughout the specification. It has been proposed at one of the TRTF calls and may move forward pending alignment. Would this alleviate this concern?
@peacekeeper the updated spec does not make an assumptions about the type of identifier used. This is left to the profiles that sit on top of the spec to decide.
Motion to close this ( but well received and will make it's way downstream ) to other efforts happening out of ToIP.
I understand the difference between VIDs and DIDs, but I think the term "VID method" isn't defined or explained anywhere. In the OpenAPI specs, there are the following endpoint and data structure:
tswg-trust-registry-protocol/api/toip-tswg-trustregistryprotocol-v2.yaml
Line 305 in a703e4c
tswg-trust-registry-protocol/api/toip-tswg-trustregistryprotocol-v2.yaml
Line 890 in a703e4c
But the description says it returns a list of DID methods. If there is no difference between VID methods and DID methods, then why use this term in the API specs? Or is the idea that in the future there could potentially be non-DID VID methods?
The text was updated successfully, but these errors were encountered: