Inline @context in examples

[filip26]

Hi,
examples related to selective disclosure contain inline @context.

{
  "type": "DataIntegrityProof",
  "cryptosuite": "ecdsa-sd-2023",
  "created": "2023-08-15T23:36:38Z",
  "verificationMethod": "did:key:zDnaepBuvsQ8cpsWrVKw8fbpGpvPeNSjVPTWoq6cRqaYzBKVP#zDnaepBuvsQ8cpsWrVKw8fbpGpvPeNSjVPTWoq6cRqaYzBKVP",
  "proofPurpose": "assertionMethod",
  "@context": [
    "https://www.w3.org/ns/credentials/v2",
    {
      "@vocab": "https://windsurf.grotto-networking.com/selective#"
    }
  ]
}

Please see this discussion
w3c/vc-data-integrity#272

@vocab should not be used in a production. Having it in examples, test vectors, could lead to confusion and security issues.

(BTW an inline @context should be banned, it only adds complexity to processing that is vulnerable to issues, nothing else)

[msporny]

@vocab should not be used in a production. Having it in examples, test vectors, could lead to confusion and security issues.

Yes, agreed.

(BTW an inline @context should be banned, it only adds complexity to processing that is vulnerable to issues, nothing else)

Yes, agreed, it's unfortunate the tests include inline contexts.

We should try to remove these if possible from the test vectors and the test suites. That said, we also don't want to destabilize implementations.

/cc @BigBlueHat @PatStLouis @Wind4Greg -- what's the plan here? I suggest we switch to a driver's license, or PRC/EAD/NatCert example.

[filip26]

another option could be https://www.w3.org/ns/credentials/examples/v2. It's consistent with other VCDM2.0 based specs.