Removed the "MUST" for error conditions to be in sync with CID and DI

[iherman]

See discussion in w3c/vc-data-integrity#327 : the handling/reporting of errors should be consistent with the DI and CID specifications.

(See also w3c/cid#140).

---

Preview | Diff

[longpd]

This aligns all our references to this topic and should be approved. +1 for that.

[iherman]

The issue was discussed in a meeting on 2025-01-22

• no resolutions were taken

View the transcript

4.3. Removed the "MUST" for error conditions to be in sync with CID and DI (pr vc-data-model#1587)

See github pull request vc-data-model#1587.

Ivan Herman: ok. we have time for one more.

Manu Sporny: we have a section on error conditions.
… it's optional to implement.
… but if they do implement it, we have some strong requirements around how they implement those errors.
… this change would not effect our current test suites since these aren't tested now because they are optional.
… so, if we reduce this from a MUST to a SHOULD to match the upstream RFC, this would not effect any implementers currently passing the test suite.

Ivan Herman: so...apparently we have a mixed approach across the specifications that use this text.

Dave Longley: +1 for consistency.

Ivan Herman: so this PR actually makes things sync up.
… whatever else we do, we need to be consistent.

Phillip Long: +1 for this PR.

Ivan Herman: comment on the PR if you'd like.
… any final comments?
… ok. I think we can close the meeting.
… brent should be back next time.
… bye all.

---

[msporny]

Editorial, multiple reviews, changes requested and made, no objections, merging.