-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Align DID document service type with Aries DID Doc conventions? #179
Comments
indeed they should match |
If this "service type", is going to look different than every other type property, it should at least be registered.... |
strong -1 to "Aries DID Document" representations super-seeding the W3C Conventions. |
@troyronda @swcurran What do you think? This could be point in time where an adjustment in Aries could be done without greater hiccups. |
I think the types should be kept separated as they have different working. The Aries RFCs Shouldn't we just interpet |
Per previous WG discussions, this intentionally does not align with DIDComm V1 (Aries) conventions in order to tell them apart. This will be discussed in today's WG meeting. |
I think its a good idea to make DIDComm v1 and DIDComm v2 distinguishable... I hate to suggest date stamping but thats also an option. It wouldn't be the end of the world if the service type were different, if it was well documented and registered. |
@TelegramSam was there an outcome to this that can be put into a PR? |
@kdenhartog I think no, but I need to chase down all the details and verify. |
This was discussed in the DIDComm WG on 20220228. It was decided to leave the description as is. |
Is the difference between the spec here and the Aries DID Document conventions on purpose or should this be aligned ?
DIF Service type: "DIDcomm"
Aries DID Doc convention service type "did-communication"
The text was updated successfully, but these errors were encountered: