-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix botched merge to main for "Other Deliverables" section. #91
Conversation
@@ -292,7 +292,7 @@ <h3> | |||
</td> | |||
</tr> | |||
<tr> | |||
<td><a href="https://json-web-proofs.github.io/json-web-proofs/">JSON Web Proof (JWP)</a></td> | |||
<td><a href="https://json-web-proofs.github.io/json-web-proofs/">VC-JSON Web Proof (JWP)</a></td> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@brentzundel @Sakurann @iherman -- just making sure each of you see this. We are standardizing VC-JWP in this group, NOT JWP. JWP will be standardized in IETF. We probably need to make this much more clear in the charter.
originally added in acronym PR
@@ -292,7 +292,7 @@ <h3> | |||
</td> | |||
</tr> | |||
<tr> | |||
<td><a href="https://json-web-proofs.github.io/json-web-proofs/">JSON Web Proof (JWP)</a></td> | |||
<td><a href="https://json-web-proofs.github.io/json-web-proofs/">VC-JSON Web Proof (JWP)</a></td> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@msporny @brentzundel -- Should VC-JSON Web Proof (JWP)
not have become VC-JSON Web Proof (VC-JWP)
(changing the parenthetical), or maybe Verifiable Credential JSON Web Proof (VC-JWP)
(changing the parenthetical and expanding VC in the full name)?
The acronym JWP was originally expanded in https://github.com/w3c/vc-wg-charter/pull/79/files, this PR added the VC, which is already expanded in the scope section. |
This PR fixes a botched merge that never made it to
main
in #86 (comment). What went wrong is explained in #77 (comment). This PR ensures that the botched merge makes it down tomain
. It already has all of the approvals to go tomain
, this PR just records what happened.Preview | Diff