- From: Nate Otto <nate@ottonomy.net>
- Date: Wed, 2 May 2018 13:14:51 -0700
- To: public-eocred-schema@w3.org
- Message-ID: <CAPk0ugmp-EmJGNysA1z4FkeXwuEVw44B7hHy-4f_YQtUf2u==Q@mail.gmail.com>
For some extra context/flavor: In Open Badges, we use the W3C Verifiable Credentials vocab/methodology to enable 3rd parties to create Endorsements that describe their recognition of a particular defined Credential. This is still early days, but in the current version of the OB vocabulary, there is a property that allows publishers to identify the "endorsements" that have been awarded to the Credential (or to the Issuer, or to the awarded instance of the credential). Because each endorsement is separately verifiable, the publisher's word doesn't need to be trusted when they describe organizations/individuals who recognize the badge. This means that the relationship is actually between the (Credential -> Endorsement -> Issuer of the Endorsement), not directly (Credential -> Issuer of the Endorsement) If we add in a recognizedBy feature in the vocabulary, it might be useful to define use cases for how this data is published (who is publishing it, where, and for what audience?) and when/why that published data should be trusted by consumers. This might yield additional properties we might need in order to support those use cases, or we might want to go the Open Badges route of modeling the Endorsement of the credential itself as an intermediate relationship. Nate
Received on Wednesday, 2 May 2018 20:15:18 UTC