Align with W3C "Linked Claim"

[robcoyle913]

Similar to 1EdTech Endorsements

[ottonomy]

Does this issue refer to this working paper from Rebooting Web of Trust? https://github.com/WebOfTrustInfo/rwot11-the-hague/blob/master/final-documents/composable-credentials.pdf

This shouldn't be described as a W3C project if so; it appears to be just a set of ideas circulating for early development and maybe eventual standards-tracking at T3 Innovation Network.

[gvelez17]

hey @robcoyle913 @ottonomy i'd love to find some ways to move the ideas forward, started a more concise write up here https://github.com/Cooperation-org/LinkedClaims/blob/main/LinkedClaimsRFC.md

[longpd]

@ottonomy is correct that this is not a formal W3C project. It has been presented to the W3C VC-EDU taskforce, which is formally under the W3C Community Credential Group (CCG). The use of hashlinks, one of the methods introduced in LinkedClaims, has also been mentioned in discussions of the VCDM v2.0 workgroup.

Golda, and her LinkedTrust organization, is part of the dev team that is involved in the development of LinkedClaims Author, along with Dmitri Zagidulin (Interop) and Karen Passmore (PredictiveUX). The core components of LC are used by the Resume Author (RA) project, as well.

RA is proof of concept resume authoring tool based on the the HR Open Standards schema. It is intended to help focus discussion within their Recruiting WG on ways to develop LER-RS v2. On thread there is exploring the implementation of this as a compound credential, wrapping individual VCs representing the sections typically included in a resume. @mleuba persuasively argued that the LER-RS as a resume should encompass all its component parts into a single object, as relying parties treat resumes today in their PDF or .docx formats. We're leveraging 1Edtechs CLRv2 and OBv3, as objects that hold education (transcripts), and single assertion achievement "types" as building blocks of the commonly found sections in resumes. The RA proof of concept VC resume is the result.

The VC represents a data model intended to guarantee interoperability. Particular use cases following its structure support different applications of it, such as a resume. Our goal, shared by T3, is leverage existing standards wherever possible and only create new domain specific credentials where needed, doing so wherever possible from existing schema standards.