Re: Plugfest 2 Technical Discussion - Recording and Notes

Hi David,

Sorry for the delay and my upcoming non-answer.  First, Terms of Service does not exist in the OBv3 schema, so please propose that by submitting an issue to
https://github.com/IMSGlobal/openbadges-specification/issues<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FIMSGlobal%2Fopenbadges-specification%2Fissues&data=05%7C01%7Csleu%40jff.org%7C8c9222702e6a4df6eccd08dab2753cbe%7C3bddf584e8d746c49804a0f3cdf0b0ca%7C0%7C0%7C638018513869071256%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=x%2FqYbSYQM5PQALYS4Cz7MIYjNuU%2FpSU8A82GVSNK%2F3k%3D&reserved=0>.  I think it would be really interesting to engage that community in a discussion about why that should be included in the spec to kick of a conversation and to hear their feedback, too.

Second, yes, Evidence Type is meant to be an array in the spec, but my understanding is that there has been several conversations so far about types (string/array) in the spec, generally, that are being reviewed.  Most of these have already been submitted as an issue, but I don’t see one for this field yet.  Perhaps you could also submit this as an issue?

In terms of plugfest, feel free to add any additional fields you think are necessary.  We would be really interested in knowing more about how you added them and why.

sharon



From: David Chadwick <d.w.chadwick@truetrust.co.uk>
Date: Thursday, October 20, 2022 at 4:29 AM
To: Sharon Leu <sleu@jff.org>, public-vc-edu@w3.org <public-vc-edu@w3.org>
Subject: Re: Plugfest 2 Technical Discussion - Recording and Notes

Hi Sharon

We should be able to use this schema for our basic credential with the minimum of properties, but when we add terms of use and evidence it might give us a problem. First there is no Terms of Use in your schema (could you add it please?) and secondly your Evidence  type is required to be set to 'Evidence' whereas we use a URI to denote eIDAS authentication. So if you could make type mandatory but the value any URI that would satisfy us

Kind regards

David
On 19/10/2022 21:51, Sharon Leu wrote:
Hi David,
You are correct. Use any schema validator, but be sure to validate against OBv3 schema: https://purl.imsglobal.org/spec/ob/v3p0/schema/json/ob_v3p0_achievementcredential_schema.json<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flinkprotect.cudasvc.com%2Furl%3Fa%3Dhttps%253a%252f%252fpurl.imsglobal.org%252fspec%252fob%252fv3p0%252fschema%252fjson%252fob_v3p0_achievementcredential_schema.json%26c%3DE%2C1%2CU_l1eoIMJ9u-4uzvtUTgAWrRkQMiteTeyBbLFp5jp5TdW5RXo-Hy-ALn-WZCfC-LDtRrb63mJsZqLZHOln3WTWjNh-6LE16m_RX4CVmHc3A6g6qGmbsHWZ1G1w%2C%2C%26typo%3D1&data=05%7C01%7Csleu%40jff.org%7C8c9222702e6a4df6eccd08dab2753cbe%7C3bddf584e8d746c49804a0f3cdf0b0ca%7C0%7C0%7C638018513869071256%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=SB46evMTxAQ7yZKJBH%2Bhy6mPuk994fwpt7UtqBbptuI%3D&reserved=0>.

sharon

From: David Chadwick <d.w.chadwick@truetrust.co.uk><mailto:d.w.chadwick@truetrust.co.uk>
Date: Wednesday, October 19, 2022 at 4:22 PM
To: public-vc-edu@w3.org<mailto:public-vc-edu@w3.org> <public-vc-edu@w3.org><mailto:public-vc-edu@w3.org>
Subject: Re: Plugfest 2 Technical Discussion - Recording and Notes

Hi Sharon

concerning the validation of the issued credential with a schema validator, as you know there are many of these as there is no single standard for a JSON schema. So I presume we can use the schema validator that we already use in our code (and that we insert into the credentialSchema property of the VCs we issue)

Kind regards

David
On 19/10/2022 20:50, Sharon Leu wrote:
Thanks to all who were able to participate in this conversation.  Apologies again for the change in times, we realize we were not able to accommodate everyone.

You can view and re-view the meeting using this link and password (note that the last character is a “.”):
https://us06web.zoom.us/rec/share/lCDHY6n3O8XRrw2MywykoExm52U6fT5OAygtxYLGOrm-L-q0PmnofHDCldFnjeVO.SzlcR6KPI0FEHIQW<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fus06web.zoom.us%2Frec%2Fshare%2FlCDHY6n3O8XRrw2MywykoExm52U6fT5OAygtxYLGOrm-L-q0PmnofHDCldFnjeVO.SzlcR6KPI0FEHIQW&data=05%7C01%7Csleu%40jff.org%7C8c9222702e6a4df6eccd08dab2753cbe%7C3bddf584e8d746c49804a0f3cdf0b0ca%7C0%7C0%7C638018513869071256%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=QtK2sgJyfzmh8L40EqOpn3U5BRKNxeoXpp5DcjPkOHY%3D&reserved=0>
Passcode: s#=YE4k.

Summary of key discussion items (there were others):


  1.  Spec Review. Kerri will work on updating the sample badge based on a few items we discussed today so it aligns better with the plugfest1 sample badge.
Unsigned badge: https://w3c-ccg.github.io/vc-ed/plugfest-2-2022/unsigned-badge-example-p2.json<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flinkprotect.cudasvc.com%2Furl%3Fa%3Dhttps%253a%252f%252fw3c-ccg.github.io%252fvc-ed%252fplugfest-2-2022%252funsigned-badge-example-p2.json%26c%3DE%2C1%2C00kTVqVx1LP2h8ynV3J-kX8bZHfWGUb7nSrGbbzQUS7Na4a1HRPf4U4HCP1z84P3nwomzM95mIdzghrDJQNb53aTpHhKLD4Ej1bI4vyA6lynpfyasmdezms95w%2C%2C%26typo%3D1&data=05%7C01%7Csleu%40jff.org%7C8c9222702e6a4df6eccd08dab2753cbe%7C3bddf584e8d746c49804a0f3cdf0b0ca%7C0%7C0%7C638018513869071256%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=B6GSw9%2BxDX5ZQXyeTieEFLJm%2BfyMnyBu9Aw0fcH4t50%3D&reserved=0>
Signed badge: https://w3c-ccg.github.io/vc-ed/plugfest-2-2022/signed_badge_example-p2.json<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flinkprotect.cudasvc.com%2Furl%3Fa%3Dhttps%253a%252f%252fw3c-ccg.github.io%252fvc-ed%252fplugfest-2-2022%252fsigned_badge_example-p2.json%26c%3DE%2C1%2C1Hm1mUDz74Ad6NGCALLOHMywTbcSJqnt9VLOy1NdhxCn6Ya1IYtNfSdDWVMEayS0wdJSY6yOBhyIcThvRw0_XJgoG3ph7HZtkY4PFaIS2JRccMl47SIrampimg%2C%2C%26typo%3D1&data=05%7C01%7Csleu%40jff.org%7C8c9222702e6a4df6eccd08dab2753cbe%7C3bddf584e8d746c49804a0f3cdf0b0ca%7C0%7C0%7C638018513869071256%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=KUuoiMOqUL1nAt7sceYHvdsHkPW9k4Vkqz3KILM6epk%3D&reserved=0>


  1.  OBv3 Issues. A number of questions arose on specific items in the spec. Kerri and others have raised them, but this community of users (including anyone not participating in plugfest that uses VCs or open badges, are encouraged to contribute to one of the existing issues or submit one of their own

https://github.com/IMSGlobal/openbadges-specification/issues<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FIMSGlobal%2Fopenbadges-specification%2Fissues&data=05%7C01%7Csleu%40jff.org%7C8c9222702e6a4df6eccd08dab2753cbe%7C3bddf584e8d746c49804a0f3cdf0b0ca%7C0%7C0%7C638018513869071256%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=x%2FqYbSYQM5PQALYS4Cz7MIYjNuU%2FpSU8A82GVSNK%2F3k%3D&reserved=0>


  1.  Final Deliverables. An update to the FAQ is coming soon. We are thinking:

1.       Videos due on November 8, 2022 at 12 PM ET

1.       Video is max 3 min in length

2.       Video includes test of your credential using schema validator

2.       Submit documentation that will allow viewers of video to reproduce the demo they are watching – could be instructions on how to use apps in the App store or login using test account, etc.

3.       Submit raw file of signed credentials

Enjoy the show and reach out if there is anything we should continue to discuss!
sharon