blockchain-certificates / cert-schema Goto Github PK

Having an issuing parsing https://www.w3.org/2018/credentials/v1 to completeness.

Issuing seems to be around the @protected field:

{
  "@context": {
    "@version": 1.1,
    "@protected": true,
...
}

Throws an error related to context being wrong.

Temp workaround is by preloading the context without the protected field. It may either be a limitation with the python implementation of json ld, an out of date library, etc.

In the spec, type should be an array of types mapping to the @context values. The second type is optional as per the spec, but would be good practice: https://www.w3.org/TR/vc-data-model/#types.

Furthermore, after reporting an issue to VCJS, this answer highlights the potential need to use a second type:

While the second type might be optional in the spec (this could be an error) the second type is essentially required as it provides a JSON-LD term that should be found in one of the @context schema or vocabularies that in turn identifies your VC in the graph. Terms not found in a schema or vocabulary will throw in vc-js.

from digitalbazaar/vc#45 (comment)

in example blockcerts: https://github.com/blockchain-certificates/cert-verifier-js/blob/master/test/fixtures/blockcerts-3.0-alpha.json

https://github.com/blockchain-certificates/cert-schema/blob/master/examples/3.0-alpha/exampleVerifiableCredential.json#L9

19:73?

First, a quick fix: V2_1_SCHEMA_LOCAL_PATH points to v2.0, as shown here:

However, this doesn't seem to solve the whole problem. Certificates I tested still seem to pass v2.1 validation only to cause the blockcerts-verifier verification dialog (with the checkmark) to throw an error and not display at all.

Let me know if I'm overlooking something here since I'm not familiar with v2.1 (haven't seen it in cert-tools etc.) and am issuing using the usual v2 tools.