Orie Steele

I suggest the following: 1. evidence is removed from the core spec and added as an extension to vc-specs-dir. 2. evidence is added to the core spec AFTER 2 implementations...

Example from Open Badges ```json "evidence": [ { "id": "https://1edtech.edu/credentials/3732/evidence/1", "type": "Evidence" , "narrative": "# Final Project Report \n This project was ...", "name": "Final Project Report", "description": "This is...

Example from [OIDF eKYC and IDA Evidence](https://docs.google.com/document/d/1htujrb-_1kh8tkV4MXYRmZ44m_D7yFrY09aFJkAz7io/) ```json { "evidence": [{ "type": ["https://openid.bitbucket.io/ekyc/openid-connect-4-identity-assurance.html#name-verification-element"], "verification": { "trust_framework": "uk_tfida", "scheme": "idconnect", "assurance_level": "idconnect_kyc_partial", "assurance_process": { "policy": "GPG_45", "scheme_policy": "idconnect_kyc", "procedure": "L1B", "scheme_procedure":...

Based on the 2 examples in the vc-specs dir, it seems people are using "type" in different ways... if there are 2 independent implementations of either of these, I think...

Related issue: https://github.com/w3c/vc-data-model/issues/893

There should be 2 places where tests are improved: 1. tests for the core data model 2. tests for securing formats that use evidence I'm not volunteering to do either...

Ideally we could test both conformance to the data model, and business logic associated with evidence production and consumption. The latter would need to be in a different test suite...

It's already been requested to be registered here: https://w3c.github.io/json-ld-syntax/#structured-extension-ld-json It's blocked pending the multiple suffixes draft, as are all media types including multiple plus signs.

You can implement a detached sign / verify API, by wrapping this API and encoding / decoding to extract to set the payload.

We should make sure we point to https://github.com/decentralized-identity/ion until we can fully support it in this code base.