- From: Kerri Lemoie <klemoie@mit.edu>
- Date: Thu, 3 Nov 2022 22:00:57 +0000
- To: David Chadwick <david.chadwick@crosswordcybersecurity.com>
- CC: Sharon Leu <sleu@jff.org>, "public-vc-edu@w3.org" <public-vc-edu@w3.org>, Simone Ravaioli <simone.ravaioli@parchment.com>, "dzagidulin@gmail.com" <dzagidulin@gmail.com>, Joan <jlee@jfflabs.org>, Stephanie Correa <scorrea@jff.org>
- Message-ID: <CF9D038F-7F7F-4254-975C-24D933AD3C2D@mit.edu>
Hi David, Thanks for the great questions. I’m going to answer the easier ones first: ii) Since the logo is now being incorporated as a URL, rather than being embedded, it is dependent upon the user to click on the URL when looking at the VC in their wallet. This will bring up the browser to display whatever is at this endpoint. Do you require the user to do this in the demo, since this is browser functionality rather than wallet functionality? It isn’t required to display the logo only that it is being included in the VC. It could be a URL or it could be embedded. It would be nice to see it displayed, but not required. iii) Getting wallet apps into Apple's iStore can be a long and laborious process. If wallet providers have not completed this process by the demo submission date can you suggest a fallback? Yes- excellent point. The aim is for replicability but that said, working with the mobile app stores can definitely be a long and laborious process. Also acceptable, is an accessible test flight, google console, etc.. instance. A last option is to provide access to the code repo with instructions and how to build. If you have a suggestion that’s different but similar to these, let us know. i) regarding conformance to the schema, it may be difficult for wallet providers to do this. What we have done (as an issuer) is to use Postman to connect to our issuer, then display the contents of the VC that is returned and show that it conforms to the schema by pasting it into the schema checker. Would it be OK for the wallets that are testing against our issuer to use this video. iv) Regarding the raw signed VC, again it may be difficult for some wallets to show or export it since it is not a user friendly feature to provide. Will the solution suggested in i) above be OK for this? Some thoughts on this and curious what you think. Ideally, we want to be able to know that the signed badge conforms to the schema and is the same signed badge coming from the issuer that is in the wallet. It's ok for the wallet to show what you’ve described but also should demonstrate that the same credential conforms to the schema after it is in the wallet by pasting it into the schema checker again in the video. Agree that displaying raw code is not a particularly user friendly option, so the wallet could decide instead to print the badge to a log after it’s been added to the wallet to use for the schema validation and providing of raw badge code. The replication steps will be the most helpful for the plugfest team but having it in the video gives others an opportunity to see it too. Thanks, K. On Nov 3, 2022, at 4:11 AM, David Chadwick <david.chadwick@crosswordcybersecurity.com<mailto:david.chadwick@crosswordcybersecurity.com>> wrote: Hi Sharon thankyou very much for these instructions. I have a few queries and suggestions i) regarding conformance to the schema, it may be difficult for wallet providers to do this. What we have done (as an issuer) is to use Postman to connect to our issuer, then display the contents of the VC that is returned and show that it conforms to the schema by pasting it into the schema checker. Would it be OK for the wallets that are testing against our issuer to use this video. ii) Since the logo is now being incorporated as a URL, rather than being embedded, it is dependent upon the user to click on the URL when looking at the VC in their wallet. This will bring up the browser to display whatever is at this endpoint. Do you require the user to do this in the demo, since this is browser functionality rather than wallet functionality? iii) Getting wallet apps into Apple's iStore can be a long and laborious process. If wallet providers have not completed this process by the demo submission date can you suggest a fallback? iv) Regarding the raw signed VC, again it may be difficult for some wallets to show or export it since it is not a user friendly feature to provide. Will the solution suggested in i) above be OK for this? Kind regards David On 02/11/2022 23:35, Sharon Leu wrote: Hello Plugfest 2 friends and observers, Demo day is fast approaching and at long last and finally do are the instructions on how to participate in demo day and submission requirements. For this plugfest, the requirements differ depending on if an organization is participating as a wallet provider, credential issuer, or both. In general: * All wallet providers are required to submit a video * Credential issuers can either (1) submit a video; or (2) be featured in partner videos All demo day packages are due by November 8, 2022 at 12 PM ET. Please consult the Plugfest2 Participation Guide<https://docs.google.com/document/d/1902XicCS_10x_zzGFabk65vQyxbEG2nofaSHcSd6G8A/edit?usp=sharing> for detailed instructions, especially pages 4 to 8. A general agenda is below, with details to follow later this week. Please reach out if you have any questions. sharon Demo Day Agenda Overview Monday, November 14, 2022 9 AM PT Start 9:25 AM VC-API/CHAPI Demos and Discussion 10:25 AM OIDC Demos and Discussion Intermission 11:35 AM DIDCommv2 Demos and Discussion 12:25 PM Debrief and Plugfest3 Planning Time: Nov 14, 2022 09:00 AM Pacific Time (US and Canada) https://us06web.zoom.us/j/83917181963?pwd=YjA1SUFPN2RSUHg4a09seDRlRHdQdz09 Meeting ID: 839 1718 1963 Passcode: 623227
Received on Thursday, 3 November 2022 22:03:14 UTC