Unum ID enables securely sharing verified
We opted to format our data using W3C's Linked Data serialized via JSON-LD. It gives us the structure to create a data validation framework along with a human readable vocabulary around the data. We feel this meets our goal to have a credential schema definition that is robust enough to encapsulate and define any data with the property of being easily displayed and validated.
Our entire human readable JSON-LD context semantics file can be download and viewed via, https://schema.unumid.co/context. The context file serves as a building block for the basis for the shared vocabulary that ultimately make up our credential data schemas. However more than likely as an
To view all of the Unum ID defined credential schemas one can do so via, https://schema.unumid.co/schema. If you want to know the schema for a particular credential type one can use that same url with the desired credential
type as a query param, for example https://schema.unumid.co/schema?type=EmailCredential.
Given use of JSON-LD standard for schema definitions we hope it make Issuer defined credentials schemas a reality very soon. However, until then, all credential types have schemas defined by Unum ID. Please let us know if you would like to define a new credential schema for your use case.
We currently are opting to only support what can be referred to as "single attribute atomic credentials". This means that we break data into into it simplest form for every credential. This is to provide users a means of selective disclosure for
/*The credential data compliant with the Address and FullName Credentials schemas*/
const credentialDataList = [
const unumDtoCredentialResponse: UnumDto<Credential> = await issueCredentials(