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)
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):
- 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
- 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
- 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