Replies: 0 comments 7 replies
-
NFC isn't always going to be available because it requires a hardware aspect. Support for NFC should be added, but I wouldn't expect this to be a v0.1 feature. Additionally, it would make sense to move this work over to the DIDComm WG as a way to define how the transport should be used to exchange any DIDComm message. |
Beta Was this translation helpful? Give feedback.
-
if your flow is URI based, and you embed the URI in an ndef tag, you are kinda done. I would encourage us try and stick to URIs as much as possible for this reason, especially when considering QR Codes of objects vs QR Codes that encode objects in an URI. |
Beta Was this translation helpful? Give feedback.
-
Maybe we can add a section to the spec covering NFC recommendations for DIDComm when they are available. |
Beta Was this translation helpful? Give feedback.
-
Yeah I think this is a perfect example of that the transport extensibility in DIDComm was intentionally designed. My suggestion is to work on something similar to the DIDComm Bluetooth transport but with NFC instead. |
Beta Was this translation helpful? Give feedback.
-
I'm not too familiar with NFC but a problem I see with that flow might be that the invitation must be unique per presentation so the NFC tag or whatever would need to be updated with a new invitation frequently.. |
Beta Was this translation helpful? Give feedback.
-
NFC could be identical to QR. Suggestion is to use the NDEF protocol of
NFC which is open and support on most phones, though Apple does not wake up.
…On Tue, 26 Oct 2021, 8:49 am Brian Richter, ***@***.***> wrote:
I'm not too familiar with NFC but a problem I see with that flow might be
that the invitation must be unique per presentation so the NFC tag or
whatever would need to be updated with a new invitation frequently..
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/decentralized-identity/waci-presentation-exchange/issues/16#issuecomment-951358740>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALHJPBGUZUJ6R7OATTT43ATUIXGG7ANCNFSM45CJQ43A>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Beta Was this translation helpful? Give feedback.
-
This appears blocked by DIDComm v2 support for Bluetooth and NFC... See decentralized-identity/didcomm-messaging#222 |
Beta Was this translation helpful? Give feedback.
-
NFC is a much smoother UX ... and is almost identical to the QR flow. Can this be added as an alternate, using the NDEF protocol?
Beta Was this translation helpful? Give feedback.
All reactions