jolocom/jolocom-sdk

Ok, giving up after wrapping my head for too long around JSON-LD and custom (nested) credentials. I have a (nested) claim that looks like this:

{
  "provider": {
    "type": "ImmunizationProvider",
    "name": "John Doe"
  }
}

instead like that:

  {
    "email": "foo@bar"
  }

Since you're relying on JSON-LD verification / RDF normalization under the hood, I'm supposed to send metadata describing the schema along. My current try is:

 const metadata = {
  fieldNames: ['provider'],
  optionalFieldNames: [],
  type: "ProofOfProviderCredential",
  name: "proofs you're a provider",
  claimInterface: {
    provider: {
      type: "",
      name: "",
    }
  },
  context: [{
    ProofOfProvider: "https://example.com/terms/ProofOfProviderCredential", 
    schema: "https://schema.org",
    provider: "schema:person"
  }]
}

const signedCredential = await agent.signedCredential({
  metadata,
  subject: <some-did>,
  claim: {
    provider: {
      type: "ImmunizationProvider",
      name: "John Doe",
    }
  }
})

and the result looks like

{
  "@context": [
    {
      "id": "@id",
      "type": "@type",
      "cred": "https://w3id.org/credentials#",
      "schema": "http://schema.org/",
      "dc": "http://purl.org/dc/terms/",
      "xsd": "http://www.w3.org/2001/XMLSchema#",
      "sec": "https://w3id.org/security#",
      "Credential": "cred:Credential",
  ... ... ...
    },
    {
      "ProofOfProvider": "https://example.com/terms/ProofOfProviderCredential",
      "schema": "http://schema.org/",
      "provider": {
        "@id": "schema:person",
        "@type": "@id"
      }
    }
  ],
  "id": "claimId:d2a711b3a6655906",
  "issuer": "did:jun:ESgcd47lYOODgJQ4WUP1kVyP1BpeanZfhFvI0sIrYN6w",
  "issued": "2021-03-23T18:30:11.628Z",
  "type": [
    "VerifiableCredential",
    "ProofOfProvider"
  ],
  "expires": "2022-03-23T18:30:11.626Z",
  "proof": {
    "created": "2021-03-23T18:30:11.628Z",
    "type": "EcdsaKoblitzSignature2016",
    "nonce": "b11c28c28fd64364",
    "signatureValue": "f845caa9ff61d36238979fede170a0dea48699fc53a9cf16c0f026ed3bf25047036e211a113697f0d51b45c99bccea1edd7c61314e5e35dfdfbc4e6b1c402201",
    "creator": "did:jun:ESgcd47lYOODgJQ4WUP1kVyP1BpeanZfhFvI0sIrYN6w#Djg_ceBWaXIy7JdiO-HfQK-wVaF2u0OMDr5yIARfDCJM"
  },
  "claim": {
    "provider": {
      "type": "ImmunizationProvider",
      "name": "John Doe"
    },
    "id": "did:key:z6MkuSH7TFfdcGSBLriB5jAjfqKbbWf1C3qPhqJwSJTqdWL8"
  },
  "name": "VerifiableCredential,ProofOfProvider"
}

the normalization isn't working here: When I change the claim's key property name (provider => proVider), the verification fails. If I change anything inside the provider object, it verifies fine (the signature isn't taking these fields into account).

Question:

How do I define a schema that allows this kind of nested claims? (there'll be much more nesting going on in the real case, btw, similar to: https://github.com/smart-on-fhir/health-cards-tests/blob/master/src/fixtures/vc-covid-immunization.json)

btw, when using https://w3id.org/credentials/v1 in the schema, the agent throws jsonld.ProcessingModeConflict: @version: 1.1 not compatible with json-ld-1.0 but I guess that's due to an outdated dependency under the hood.