Updated driver details for did-elem

[BenjaminMoe]

Changes:

• did:elem was updated to did:elem:ropsten to avoid confusion as did:elem is reserved for mainnet.
• Example curl request was updated to reflect this change
• driver in config.json was updated with regex and instance for resolving did:elem:ropsten

Issue:

#283

Example:

curl -X GET http://localhost:8080/1.0/identifiers/did:elem:ropsten:EiCtwD11AV9e1oISQRHnMJsBC3OBdYDmx8xeKeASrKaw6A

Returns

{
  "@context":"https://w3id.org/did-resolution/v1",
  "didDocument":{
    "assertionMethod":[
      "#zQ3shvfXLUVwKffPochZ1UkSjxQqpgND3Z5DhzTADooqmmypp"
    ],
    "keyAgreement":[
      "#zQ3shvfXLUVwKffPochZ1UkSjxQqpgND3Z5DhzTADooqmmypp"
    ],
    "id":"did:elem:ropsten:EiCtwD11AV9e1oISQRHnMJsBC3OBdYDmx8xeKeASrKaw6A",
    "verificationMethod":[
      {
        "id":"#zQ3shvfXLUVwKffPochZ1UkSjxQqpgND3Z5DhzTADooqmmypp",
        "controller":"did:elem:ropsten:EiCtwD11AV9e1oISQRHnMJsBC3OBdYDmx8xeKeASrKaw6A",
        "type":"JsonWebKey2020",
        "publicKeyJwk":{
          "kty":"EC",
          "crv":"secp256k1",
          "x":"7hfx9LZXlMBaZ2EurUcXOITSIGLIFQ4YY7pXCbEqntU",
          "y":"B1FId5MlHAuhxsDU9uvPuE2JXKVPP3ohjuR6HUvY6XM"
        }
      }
    ],
    "authentication":[
      "#zQ3shvfXLUVwKffPochZ1UkSjxQqpgND3Z5DhzTADooqmmypp"
    ]
  },
  "didResolutionMetadata":{
    "pattern":"^(did:elem:ropsten:.+)$",
    "driverUrl":"https://ropsten.element.transmute.industries/api/1.0/identifiers/$1",
    "duration":17783,
    "did":{
      "didString":"did:elem:ropsten:EiCtwD11AV9e1oISQRHnMJsBC3OBdYDmx8xeKeASrKaw6A",
      "methodSpecificId":"ropsten:EiCtwD11AV9e1oISQRHnMJsBC3OBdYDmx8xeKeASrKaw6A",
      "method":"elem"
    },
    "contentType":"application/did+ld+json",
    "convertedFrom":"application/did+json",
    "convertedTo":"application/did+ld+json"
  },
  "didDocumentMetadata":{
    "method":{
      "published":true,
      "recoveryCommitment":"EiB2lrE88cmhcepLS-p8wBbxHfZKSvniCKfL0CfZe4i36g",
      "updateCommitment":"EiBch3E26X_PoJ_Io2NS8-Dn6F94hcMAChZ6-AaZ2B_pUQ"
    },
    "canonicalId":"did:elem:ropsten:EiCtwD11AV9e1oISQRHnMJsBC3OBdYDmx8xeKeASrKaw6A"
  }
}

[OR13]

Worth noting that this might now work with LD Proofs because the context is being stripped by the resolver middleware.

[OR13]

curl -s -H "Accept: application/did+ld+json" https://ropsten.element.transmute.industries/api/1.0/identifiers/did:elem:ropsten:EiCtwD11AV9e1oISQRHnMJsBC3OBdYDmx8xeKeASrKaw6A

curl -s -H "Accept: application/did+json" https://ropsten.element.transmute.industries/api/1.0/identifiers/did:elem:ropsten:EiCtwD11AV9e1oISQRHnMJsBC3OBdYDmx8xeKeASrKaw6A

Universal resolver should not tamper with resolutions responses from drivers.

EDIT: imo our endpoint should probably be updated to behave the same with the universal resolver behaves.

even in cases where we think the behavior is a bug, like this.

[BenjaminMoe]

curl -s -H "Accept: application/did+json" http://localhost:8080/1.0/identifiers/did:elem:ropsten:EiCtwD11AV9e1oISQRHnMJsBC3OBdYDmx8xeKeASrKaw6A

Returns

{
  "@context": [
    "https://www.w3.org/ns/did/v1",
    "https://w3id.org/security/suites/jws-2020/v1",
    {
      "@vocab": "https://www.w3.org/ns/did#"
    }
  ],
  "id": "did:elem:ropsten:EiCtwD11AV9e1oISQRHnMJsBC3OBdYDmx8xeKeASrKaw6A",
  "verificationMethod": [
    {
      "id": "#zQ3shvfXLUVwKffPochZ1UkSjxQqpgND3Z5DhzTADooqmmypp",
      "controller": "did:elem:ropsten:EiCtwD11AV9e1oISQRHnMJsBC3OBdYDmx8xeKeASrKaw6A",
      "type": "JsonWebKey2020",
      "publicKeyJwk": {
        "kty": "EC",
        "crv": "secp256k1",
        "x": "7hfx9LZXlMBaZ2EurUcXOITSIGLIFQ4YY7pXCbEqntU",
        "y": "B1FId5MlHAuhxsDU9uvPuE2JXKVPP3ohjuR6HUvY6XM"
      }
    }
  ],
  "authentication": [
    "#zQ3shvfXLUVwKffPochZ1UkSjxQqpgND3Z5DhzTADooqmmypp"
  ],
  "assertionMethod": [
    "#zQ3shvfXLUVwKffPochZ1UkSjxQqpgND3Z5DhzTADooqmmypp"
  ],
  "keyAgreement": [
    "#zQ3shvfXLUVwKffPochZ1UkSjxQqpgND3Z5DhzTADooqmmypp"
  ]
}

[OR13]

Seems the issue is the default accept header is for a. "did resolution response" not a "did document".... and the "did resolution response" strips the context, but the "did document does not".

We should just remember to never ask for the did resolution response and we should be good on our end.