Example credentials from Parchment.com.

[BigBlueHat]

No description provided.

[BigBlueHat]

I had some issues with the VC Playground loading the https://schema.org context. IIRC, it's advised to not use that entire context, but instead bring in only the terms needed via a community supported context. Would that be the solution here?

[BigBlueHat]

Thanks for sharing these credentials, @SimoneRavaioli!

Below are a few issues I've found in their term mappings. The schema.org context includes a (rather dangerous) catch-all mapping of "@vocab": "http://schema.org/" which practically results in any "unknown" term ending up at http://schema.org/{unknownTerm}. For example, in these contexts, the following terminology need explicit mappings added to a context file, so they don't end up prefixed with http://schema.org/ incorrectly.

The following terms from the AcademicAward credential don't exist in the Schema.org vocabulary:

http://schema.org/awardDetails
http://schema.org/educationalOrganization
http://schema.org/jwt
http://schema.org/AcademicAward
http://schema.org/awardDescription
http://schema.org/awardId
http://schema.org/awardTitle
http://schema.org/awardType
http://schema.org/dateAwarded
http://schema.org/honours
http://schema.org/studyArea
http://schema.org/countryCode

And, http://schema.org/dateIssued exists, but it's narrowly defined as "The date the ticket was issued."

These terms don't appear in the other contexts, so we'll either need to find a context file that does contain those mappings or create one for this use case.

The LearnerProfile context is missing the same terms plus http://schema.org/LearnerProfile also doesn't exist and should map to something that does.

Happy to help work through this with you!

[BigBlueHat]

@SimoneRavaioli any interest in revisiting this credential?