Add DataIntegritySignature to v2 context?

[msporny]

Now that the VCWG work is under way and the CCG Data Integrity specification has been selected as the input document for the Data Integrity work, it's time to start nailing down some implementation directions for the next 2+ years.

One of the first of those considerations is streamlining the way we build Data Integrity cryptosuites and include them in the base VC v2 context. Please find proposals linked to the end of this post that that:

• Ideally, eliminates the need to create new JSON-LD Contexts for cryptosuites and include them in VCs for 80%+ of the use cases we currently have.
• Continues to ensure the ability to get large compression gains via the use of semantic compression (e.g., CBOR-LD)

The presentation deck containing the proposal is here: https://docs.google.com/presentation/d/16J9TcFc6fX18Cun_Rhj3xqNlnhkCs6MnPkGBlRL3YKg/edit

Archived copies of the proposal are here: https://lists.w3.org/Archives/Public/public-vc-wg/2022Jul/0044.html

[iherman]

The issue was discussed in a meeting on 2022-08-03

• no resolutions were taken

View the transcript

6.10. Add DataIntegritySignature to v2 context? (issue vc-data-model#901)

See github issue vc-data-model#901.

Brent Zundel: 901, also got this one wrong?.

Manu Sporny: You may be eventually correct though! There is a question about where the context lives... That's in the core repo for now..

Brent Zundel: Removing that link... Last one.

Manu Sporny: +1 to move nonce to data-integrity :).

[msporny]

This is being addressed by PR #943. This issue will be closed as soon as that PR is merged.

[Sakurann]

done! was called dataIntegrityProof

[TallTed]

Maybe worth changing issue title from DataIntegritySignature to match actual addition of dataIntegrityProof?