W3C home > Mailing lists > Public > public-credentials@w3.org > October 2020

Re: Modeling Educational Verifiable Credentials converted to spec text

From: Nate Otto <nate@ottonomy.net>
Date: Fri, 9 Oct 2020 10:40:56 -0700
Message-ID: <CAPk0ugmdCfRxLjw-_sV+1QZ72A6EgUje+y-Or0Swqkeos6dEjw@mail.gmail.com>
To: Snorre Lothar von Gohren Edwin <snorre@diwala.io>
Cc: Kim Hamilton Duffy <kimhd@mit.edu>, "W3C Credentials CG (Public List)" <public-credentials@w3.org>
Snorre,

Great question. I think that that particular aspect of that rough example
has not yet had much discussion, but that's exactly the sort of thing that
this next phase should include as we've now moved the rough drafts into
this format.

I think the wrapping the learner record inside the credentialSubject
property would probably work, for instance

"credentialSubject": {
  "learnerRecord": [{}, {}, ...]
}

This would be compatible with the VC Data Model's guidance that the
credentialSubject object MAY contain an identifier. In the case of the
assertions in the example, the identifier is hashed in Open Badges
recipient.identifier format. That may be something that the people who
submitted this example might wish to continue doing, and I don't see
anything that would necessarily block that. Coming up with partnerships to
consume data in format that some issuer has produced is going to be the
main challenge in any VC space, including here. I think there is good
opportunity in the EDU space for that sort of coordination, though
proliferation of different approaches for similar problems would complicate
that. The doc currently represents raw material, prior to those
partnerships around particular approaches developing.

*Nate Otto*
Director, Badgr Platform, Concentric Sky
badgr.com | concentricsky.com
he/him/his
Received on Friday, 9 October 2020 17:41:21 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:25:04 UTC