As discussed in the thread https://moodle.org/mod/forum/discuss.php?d=347762, I create this issue about upgrade current Moodle Badge plugin to apply Open Badge Specification Version 2.0

The updates of Open Badge Specification version 2.0: https://openbadgespec.org/history/2.0.html

• Optional new features:
  • Endorsement (#73, #76, #79)
  • Embed Criteria into a BadgeClass, including a rich (Markdown) text field, narrative. (#74)
  • Embed Evidence metadata into an Assertion, and connect multiple pieces of evidence through a narrative in Markdown text. (#84)
  • Embed Image information into Badge Objects, enabling greater accessibility of Open Badges. (#82)
  • Internationalization and multi-lingual badges are now available (#1)
  • Version control and references to previous/other versions of Badge Objects, specifically BadgeClasses. (#53)
  • Embed metadata about badge images (#85)
  • Award badges to identity types other than email with more explicit instructions (note: backpacks will continue to primarily support email, but we can move the market forward together with this framework) (#77)
  • Improved alignment to external frameworks and objectives (#81)
    **
• Breaking changes:
  • Linked Data in JSON-LD is now the official data model and syntax of Open Badges. This minimally affects issuers, who were already publishing v1.1 badges in JSON-LD, but all verifiers, backpacks, and displayers of badges must now explicitly perform a JSON-LD expansion/contraction operation to guarantee data integrity before further analysis of any object in the Open Badges context. This is a simplification from the hybrid approach introduced in v1.1 that required issuers to both use valid linked data properties and specific property names.
  • The AlignmentObject has been updated to use different terminology. Displayers will be asked to handle the new terms, which is now explicitly based on the schema.org/AlignmentObject class. "description" -> "targetDescription"; "url" -> "targetUrl"
  • BadgeClasses may now be embedded into Assertions, Issuers into BadgeClasses, and JSON-LD representations of Criteria, Evidence, and Images may now be embedded into fields that previously expected a URI string value. These new vocabulary classes improve portability, expressiveness, and accessibility of Open Badges. Optional for issuers.
  • VerificationObjects have been improved (#87, #80, #78). Hosted verification uses the id property, so verify.url duplication is no longer required or expected (#78). Signed badges are no longer required to discover a key from a url in the Assertion that signs them, closing a security hole. Instead, keys must be linked from the issuer Profile (#89).
  • RevocationList documents (used by less than 1% of issuers) are now published under an improved Linked Data class (#33)
  • Timestamps should appear in a consistent format (#86)

I'm from Nashtech Global. Our client, Open University suggest us to do this improvement and distribute to Moodle community. I hope to receive feedbacks from Moodle Dev team soon.