Separate verification from validation in verification algorithm about vc-data-model

[msporny]

It is not clear to me exactly what concrete specification text we need to write to address this concern. It might be related to this change suggestion.

@OR13 please edit the initial issue text to elaborate on what changes you'd like to see in the specification.

[OR13]

@msporny the key concept I would like to see is "sharing of validation".

After verification, you have a JSON-LD document that might be conformant.

It should be possible to craft the language, such that the exact same algorithm applies to validating both verified data integrity proof secured and verified sd-jwt secured JSON-LD documents.

Status checks and schema checks can also be shared, assuming that is desirable.

[msporny]

@OR13 I believe PR #1381 addresses the concern you raised above (because it uses a suggestion you requested in a separate thread). Once PR #1381 is merged, this issue will be closed.

[iherman]

The issue was discussed in a meeting on 2023-12-13

• no resolutions were taken

View the transcript

2.10. Separate verification from validation in verification algorithm (issue vc-data-model#1376)

See github issue vc-data-model#1376.

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

Brent Zundel: separate verification and validation, PRs exist.
… we have discussed, seems it is on a good trajectory.
… comments?

[msporny]

PR #1381 has been merged, closing.