Support of SHACL Schema in Version 2.0 about vc-data-model

[iherman]

Apologies for being formal at this point, but it is also my role with my staff contact's hat on...

The discussions and the issues in #1416 (comment) and in #1416 (comment) show that such a support is far from technically obvious, and would require a normative addition to the specification. However, the VCDM model has just been approved to move to Candidate Recommendation on the 1st of February, and the VC JSON Schema spec is already in Candidate Recommendation phase. This means we are now in a feature freeze state, and the WG should not consider adding new normative features.

I am not against continuing the discussion, but we should raise the 'future' flag for this issue, as well as for #1416 and #1411.

@brentzundel

[iherman]

The issue was discussed in a meeting on 2024-01-31

• no resolutions were taken

View the transcript

2.3. Support of SHACL Schema in Version 2.0 (issue vc-data-model#1419)

See github issue vc-data-model#1419.

Brent Zundel: We already had a conversation about this one through the PR that was raised, this is the SHACL one. At this point, it seems likely we'll just label this future but we should allow the conversation to come to completion on the PR before making that designation here.
… Happy to take comments if folks have them, otherwise moving on.

[iherman]

I think this issue should be closed. @brentzundel ?

[brentzundel]

The related PR has been closed. Closing this issue as consensus to make these changes was not found.