Re: Plugfest 2 Technical Discussion - Recording and Notes

Hello all,

Here’s a summary of the OBv3 issues. Once we get the word that the updates have been made to the spec (will take a few days), we’ll update the examples on the plugfest page too.


For these issues, it was. Agreed that type coercion would be allowed and that arrays would not be specifically required.
Achievement Type Question #469<https://github.com/IMSGlobal/openbadges-specification/issues/469>
Issuer Type Question #470<https://github.com/IMSGlobal/openbadges-specification/issues/470>
credentialSubject Type Question #471<https://github.com/IMSGlobal/openbadges-specification/issues/471>
Proof Array Question #473<https://github.com/IMSGlobal/openbadges-specification/issues/473>


Proof Requirement #476<https://github.com/IMSGlobal/openbadges-specification/issues/476> - an embedded proof is not required to accommodate JWT serialization but the spec content will be updated to add more clarification

Required Items for Proof #472<https://github.com/IMSGlobal/openbadges-specification/issues/472> - these properties will not be required because the properties of proof are dependent on the proof method. Only type is required if it is an embedded proof.


Criteria Requirements #477<https://github.com/IMSGlobal/openbadges-specification/issues/477> - this will remain open to be discussed further

AchievementCredential id<https://github.com/IMSGlobal/openbadges-specification/issues/427>  - this will remain open to be discussed further


Thanks for your input on these!


K.






On Oct 19, 2022, at 3:50 PM, Sharon Leu <sleu@jff.org<mailto:sleu@jff.org>> 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

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

Signed badge: https://w3c-ccg.github.io/vc-ed/plugfest-2-2022/signed_badge_example-p2.json



  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



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

  *   Videos due on November 8, 2022 at 12 PM ET
     *   Video is max 3 min in length
     *   Video includes test of your credential using schema validator
  *   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.
  *   Submit raw file of signed credentials


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