The Endorsement extension is deprecated since v2.0, with the addition of Endorsement to the specification.
Author: Nate Otto
Any organization that is set up to issue badges may provide endorsements of other issuers’ badge objects (Assertion, Badge Class or Issuer). For example, a school district may issue an endorsement to indicate approval of a specific Badge Class corresponding to professional development credits acceptable by the district. See the Badge Alliance Endorsement Working Group framework paper for background.
Endorsement of a Badge Class serves to publicly acknowledge the value of a badge as designed, assessed, and issued by a badge issuer. Endorsements of an Issuer are presumed to apply to all Badge Classes and Assertions created by that Issuer. See the context and schema for endorsement.
|type||type IRI array||
|description||string||The endorser’s statement about the endorsement of this particular badge class.|
|endorsedObject||object||An optional embedded copy of the endorsed Badge Object with ‘id’ attribute set.|
Extendable Badge Objects: Assertion, BadgeClass, Issuer
This extension is a little more involved in that it requires a whole Badge Class to be created for each issuer who wants to use it. From there, the extension itself must be added to an Assertion whose recipient identity is the IRI (URL) of the endorsed Badge Object. Endorsers may use one Badge Class for all their endorsements, or they may create multiple badge classes to provide different types of endorsement. Consumers should consider both the Badge Class’s
description field as well as the Assertion’s Endorsement extension’s
description property. The extension poses the option to embed the entire endorsed object so questions of intent could be resolved in case the hosted endorsed object is changed by its issuer.
BadgeClass (each endorsing issuer must define a BadgeClass to use for endorsement):
Assertion (full copy of endorsed object elided):