Deprecate digestSri.

[msporny]

Addresses issue #1628 by deprecating digestSri.

---

Preview | Diff

[longpd]

I agree and support this PR.

[kezike]

Looks good, thanks 👍🏾

[msporny]

@shigeya you noted that you plan to provide feedback on this PR. Please provide feedback soon as currently there are no objections to merging this PR.

[shigeya]

@shigeya you noted that you plan to provide feedback on this PR. Please provide feedback soon as currently there are no objections to merging this PR.

I've posted my thoughts in the issue #1628.

[iherman]

This was discussed during the vcwg meeting on 20 May 2026.

View the transcript

w3c/vc-data-model#1629

<manu> w3c/vc-data-model#1628

manu: PR to deprecate digest SRI - lots of +1s but also a push back on the issue
… raised a number of things, don't want to merge right now because it feels like he is objecting, would be good for others in group to chime in
… main concern with objections is that they are not technical in nature
… we've got to do something with the PR and issue, other opinions would be helpful in the thread

Brent: we do not have consensus to merge the PR (chair hat on) - implemented against DigestSRI our changing the spec now or changing in the future is requiring implementations to change, which is a consideration we have to take seriously
… please engage on the issue
… important discussion group needs to have

---

[iherman]

This was discussed during the vcwg meeting on 15 July 2026.

View the transcript

w3c/vc-data-model#1629

brent: This deprecates DigestSRI as an option. Several approvals but some objection bc there is an implementation that uses it.
… If you have not engaged on this and have a view, please do so.

<brent> w3c/vc-data-model#1628

Brent: In terms of spec maintenance, this is probably the major issue

brent: I believe neither Manu or Shigeya are on the call. They're the prime people for and against

---

[iherman]

This was discussed during the vcwg meeting on 05 August 2026.

View the transcript

DigestSRI - w3c/vc-data-model#1629

dlongley: believe we cannot use a copy of something that's in another spec without processing rules applying

dmitriz: goal for the PR was "now what?" - have reasoning for deprecating digest SRI / manu and shigeya prior conversation - no consensus and Shigeya's concerns are not addressed.

brent: if not resolved by TPAC - seek consensus there / doesn't feel urgent

<dlongley> hopefully a "this is deprecated and language that says other specs shouldn't use it, but it won't be removed, it will still be in the next context, etc." is a good compromise

ivan: brent is now the master of the process - which doesn't have the term "deprecate" as such, right? This is more like we have it - if you use it, has to be this way - but don't use it.

dlongley: idea is to keep it in the next version of the context - keep it around but with clearer guidance

<ivan> re deprecation see another spec: https://www.w3.org/TR/epub-34/#sec-obs-deprecated

---