Copy JWT section #1
Conversation
|
cc @selfissued @mprorock PR Previews are already working, but I don't know where this will publish after merged. |
This will merge into (essentially replace) the index.html file of the repository and will work with the github.io address, but I am sure you know that... I suspect you expect this to become automatically an official FPWD, but that is, alas!, not that simple. My apologies if you already know all that, but in case you do not:
All the admin steps will be done by yours truly, but generating the final version of the document is the responsibility of the editor. I know it is a lot of admin, but it is necessary. The FPWD step means that the documents become one of the hardcore, official documents in W3C system, it becomes part of the search index for documents, it triggers the IPR procedures, and all that. Once this is done we can set up ECHIDNA and then every such merge will also update the official version. The next time we will have to make such hard administration is when publishing a Candidate Recommendation, but that is still far away. Does this also answer w3c/vc-jws-2020#6 (comment) ? |
|
@iherman we are not planning on doing any FPWD (until we have WG resolutions), we just want a stable URL for editors drafts. Is it not possible to setup publishing for ED without going through the FPWD bit first? |
|
The editors draft URL is: That is already working and displays the empty respec shell that I created for the new repo |
| <html lang="en"> | ||
| <head> | ||
| <meta charset="utf-8"> | ||
| <meta charset="utf-8" /> | ||
| <title>JSON Web Token</title> |
There was a problem hiding this comment.
| <title>JSON Web Token</title> | |
| <title>JSON Web Token</title> |
Give there is already a JWT spec, we might want to rename the title of the spec to something like: "Securing Verifiable Credentials using JSON Web Token". I expect that might need to become the by-line (because of the size of the font for spec titles) and the title might be something like "Using JWTs for Verifiable Credentials".
There was a problem hiding this comment.
I will handle content changes in a subsequent PR, I want to keep the content as is for this one.
|
The issue was discussed in a meeting on 2022-08-03
View the transcript5.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. 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.
Brent Zundel: After the meeting, anything still labeled "vc-jwt?" will be moved to the vc-jwt repo.. |
|
The issue was discussed in a meeting on 2022-08-03
View the transcript5. Status Report: VC-JWT.See github pull request vc-jwt#1. Orie Steele: As noted by that PR, there was an agreement last time to copy over the VC-JWT section..
Orie Steele: My preference for VC-JWT is that we merge this PR; VC-JWT starts to have content under an ED.
Brent Zundel: Additional piece of business for this topic, broadly: go through issues here to transfer..
Brent Zundel: This is all the issues in the VC Data Model repository that the chairs felt were probably VC-JWT related.. |
|
With the approvals thus far, and after the conversation yesterday, I think we are clear to merge this. |
Preview | Diff