Skip to content
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

clarification of schema property #816

Merged
merged 7 commits into from
Oct 27, 2021
Merged
Show file tree
Hide file tree
Changes from 3 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
30 changes: 30 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,3 +29,33 @@ mailing list as well.

### Other useful links
* [Public group email archive](https://lists.w3.org/Archives/Public/public-vc-wg/)

## Process Overview for VC Data Model Pull Requests
1. For now, we will focus only on merging new errata PRs into this repository,
but encourage activity related to new features.
2. Once a PR is opened, chairs and editors make judgement call on whether
changes are substantive or editorial.
<dl>
<dt>Editorial</dt>
<dd>Mark with "editorial" tag, merge into branch "v1.1"</dd>
<dt>Substantive</dt>
<dd>Mark with "substantial" tag. Bugfixes are merged into separate branch "v1.2". New Features stay around as an open PR.</dd>
</dl>
3. W3C CCG is notified of PRs that will be merged in the next 14 days if there
are no objections.
4. When it's determined a new reccomendation should go out, the W3C Verifiable
Credentials Working Group members meet, review all the PRs that have been
merged, and make a formal recommendation if agreement is reached.

### Roadmap for 2021
- 1 editorial update (v1.1?)
- 1 substantive update (v1.2?)
- VC Test Suite Refactoring
- Start planning VC v2 Work, request a rechartering 3-6 months before end of
year to keep VC WG functioning.

### Focus areas
- [v1] Fixing a specific bug
- [v1] Update examples in the spec to make them modern
- [v2] VC `@context` needs updating, possibly with security vocab modularized
into smaller components instead of all included into a large context file.
114 changes: 113 additions & 1 deletion diagrams/credential-graph.svg
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
182 changes: 181 additions & 1 deletion diagrams/presentation-graph.svg
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
7 changes: 4 additions & 3 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -2462,7 +2462,7 @@ <h3>Data Schemas</h3>
<ul>
<li>
Data verification schemas, which are used to <a>verify</a> that the structure
and contents of a <a>verifiable credential</a> conform to a published schema.
and contents of a <a>credential>/a> or <a>verifiable credential</a> conform to a published schema.
</li>
<li>
Data encoding schemas, which are used to map the contents of a
Expand All @@ -2477,10 +2477,11 @@ <h3>Data Schemas</h3>
data syntax, nor enables the definition of arbitrary encodings to alternate
representation formats.
</p>

kdenhartog marked this conversation as resolved.
Show resolved Hide resolved
<p>
This specification defines the following <a>property</a> for the expression of a
data schema:
data schema, which MAY be included by an <a>issuer</a> in
kdenhartog marked this conversation as resolved.
Show resolved Hide resolved
the <a>verifiable credentials</a> that it issues:
</p>

<dl>
Expand Down