|
1 | 1 | ## Verifiable Credentials Data Model and Representations
|
2 | 2 |
|
3 |
| -Credentials are a part of our daily lives; driver's licenses are |
4 |
| -used to assert that we are capable of operating a motor vehicle, |
5 |
| -university degrees can be used to assert our level of education, |
6 |
| -and government-issued passports enable us to travel between countries. |
7 |
| -This specification provides a mechanism to express these sorts of |
8 |
| -credentials on the Web in a way that is cryptographically secure, |
| 3 | +Credentials are a part of our daily lives; driver's licenses are used to assert |
| 4 | +that we are capable of operating a motor vehicle, university degrees can be used |
| 5 | +to assert our level of education, and government-issued passports enable us to |
| 6 | +travel between countries. This specification provides a mechanism to express |
| 7 | +these sorts of credentials on the Web in a way that is cryptographically secure, |
9 | 8 | privacy respecting, and machine-verifiable.
|
10 | 9 |
|
11 | 10 | We encourage contributions meeting the [Contribution
|
12 | 11 | Guidelines](CONTRIBUTING.md). While we prefer the creation of issues
|
13 |
| -and Pull Requests in the GitHub repository, discussions often occur |
| 12 | +and Pull Requests in the GitHub repository, discussions also occur |
14 | 13 | on the
|
15 | 14 | [public-vc-wg](http://lists.w3.org/Archives/Public/public-vc-wg/)
|
16 |
| -mailing list as well. |
| 15 | +mailing list. |
17 | 16 |
|
18 | 17 | ## Verifiable Credentials Working Group
|
19 | 18 | * Group page: [https://www.w3.org/2017/vc/WG/](https://www.w3.org/2017/vc/WG/)
|
20 |
| -* charter: [https://www.w3.org/2017/vc/WG/charter.html](https://www.w3.org/2017/vc/WG/charter.html) |
| 19 | +* Charter: [https://www.w3.org/2022/06/verifiable-credentials-wg-charter.html](https://www.w3.org/2022/06/verifiable-credentials-wg-charter.html) |
21 | 20 | * Chairs
|
22 | 21 | * Brent Zundel - @brentzundel
|
23 |
| - * Wayne Chang - @wyc |
| 22 | + * Kristina Yasuda - @Sakurann |
24 | 23 |
|
25 | 24 | ### Verifiable Credentials github repos
|
26 |
| -* [Data Model](https://github.com/w3c/vc-data-model) |
27 | 25 | * [Use Cases](https://github.com/w3c/vc-use-cases)
|
| 26 | +* [Data Model](https://github.com/w3c/vc-data-model) |
| 27 | +* [Implementation Guide](https://github.com/w3c/vc-imp-guide/) |
28 | 28 | * [Data Model Test Cases](https://github.com/w3c/vc-test-suite)
|
29 | 29 |
|
30 |
| -### Other useful links |
31 |
| -* [Public group email archive](https://lists.w3.org/Archives/Public/public-vc-wg/) |
| 30 | +### Discussion Forums |
| 31 | +* [W3C Credentials Community Group Mailing List (Incubation)](https://lists.w3.org/Archives/Public/public-credentials/) |
| 32 | +* [W3C Verifiable Credentials WG Mailing List (Standardization)](https://lists.w3.org/Archives/Public/public-vc-wg/) |
32 | 33 |
|
33 | 34 | ## Process Overview for VC Data Model Pull Requests
|
34 |
| -1. For now, we will focus only on merging new errata PRs into this repository, |
35 |
| - but encourage activity related to new features. |
36 |
| -2. Once a PR is opened, chairs and editors make judgement call on whether |
37 |
| - changes are substantive or editorial. |
| 35 | +1. Anyone can open a PR on the repository. Note that for the PR to be merged, |
| 36 | + the individual must agree to the |
| 37 | + [W3C Patent Policy](https://www.w3.org/Consortium/Patent-Policy/). |
| 38 | +2. Once a PR is opened on the `v2.0` branch, chairs and editors make judgement |
| 39 | + call on whether changes are substantive or editorial. |
38 | 40 | <dl>
|
39 | 41 | <dt>Editorial</dt>
|
40 |
| - <dd>Mark with "editorial" tag, merge into branch "v1.1"</dd> |
| 42 | + <dd>Mark with "editorial" tag</dd> |
41 | 43 | <dt>Substantive</dt>
|
42 |
| - <dd>Mark with "substantial" tag. Bug fixes are merged into separate branch "v1.2". New Features stay around as an open PR.</dd> |
| 44 | + <dd>Mark with "substantive" tag.</dd> |
43 | 45 | </dl>
|
44 |
| -3. W3C CCG is notified of PRs that will be merged in the next 14 days if there |
45 |
| - are no objections. |
46 |
| -4. When it's determined a new recommendation should go out, the W3C Verifiable |
47 |
| - Credentials Working Group members meet, review all the PRs that have been |
48 |
| - merged, and make a formal recommendation if agreement is reached. |
49 |
| - |
50 |
| -### Roadmap for 2021 |
51 |
| -- one editorial update (v1.1?) |
52 |
| -- one substantive update (v1.2?) |
53 |
| - |
54 |
| -- VC Test Suite Refactoring |
55 |
| -- Start planning VC v2 Work, request a rechartering 3-6 months before end of |
56 |
| - year to keep VC WG functioning. |
57 |
| - |
58 |
| -### Focus areas |
59 |
| -- [v1] Fixing a specific bug |
60 |
| -- [v1] Update examples in the spec to make them modern |
61 |
| -- [v2] VC `@context` needs updating, possibly with security vocab modularized |
62 |
| - into smaller components instead of all included into a large context file. |
| 46 | +3. W3C CCG is automatically notified of PRs as they are raised and discussed. |
| 47 | +4. PRs are merged in 7 days if there is adequate review, as determined by |
| 48 | + the Chairs and Editors, and no objections. |
| 49 | + |
| 50 | +### Roadmap for 2022-2024 |
| 51 | + |
| 52 | +The VCWG has a set of |
| 53 | +[deliverables](https://www.w3.org/2022/06/verifiable-credentials-wg-charter.html#deliverables) |
| 54 | +and a |
| 55 | +[timeline](https://www.w3.org/2022/06/verifiable-credentials-wg-charter.html#timeline) |
| 56 | +listed in the most recent |
| 57 | +[VCWG charter](https://www.w3.org/2022/06/verifiable-credentials-wg-charter.html) |
63 | 58 |
|
64 | 59 | ### Debugging Github Pages Build Errors
|
65 | 60 |
|
|
0 commit comments