Migrate Section 6.3.1 JSON Web Token to separate normative specification

[msporny]

The VC2WG is focusing on standardizing a variety of cryptosuites. The VC2WG charter specifically calls out "Cryptosuites for VC-JSON Web Token (JWT)". We should migrate Section 6.3.1 JSON Web Token to a separate normative specification and reduce the section on proof formats to a series of links to the other normative cryptosuite specifications.

[OR13]

PR is up here: https://github.com/w3c/vc-jwt/pull/1

[Sakurann]

suggest closing this one once a PR in vc-jwt repository is merged

[iherman]

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

• no resolutions were taken

View the transcript

5.10. Migrate Section 6.3.1 JSON Web Token to separate normative specification (issue vc-data-model#880)

See github issue vc-data-model#880.

Kristina Yasuda: Not sure if it's done already.
… or if PR is there but not merged..
… This is less a move-it and rather a close-it, right?.

Manu Sporny: +1 to that. I think Kristina suggested as much in the last comment on the issue.

Michael Jones: I think this is being accomplished by VC-JWT PR 1.

Brent Zundel: I will take off the vc-jwt? label.

Michael Jones: Maybe reference VC-JWT pull-request 1.

See github pull request vc-jwt#1.

Brent Zundel: looks like that's in the comment from Orie.
… Thank you all for going through these.

Michael Jones: +1.

Brent Zundel: After the meeting, anything still labeled "vc-jwt?" will be moved to the vc-jwt repo..

[OR13]

This issue should be closed.

[brentzundel]

The associated PR has been merged, closing