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.

Sign up for GitHub

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

Jump to bottom

Clean up capitalization. #104

Merged
merged 3 commits into from
Mar 24, 2022
Merged

Clean up capitalization. #104

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
32d4172
Clean up capitalization.
msporny Mar 23, 2022
dfc07ca
Merge branch 'main' into msporny-editorial-cleanup
iherman Mar 24, 2022
0e0eed1
Apply suggestions from code review
brentzundel Mar 24, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 16 additions & 16 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -80,7 +80,7 @@ <h1 id="title"><i class="todo">PROPOSED</i> Verifiable Credentials Working Group
Readers that are new to this work should read the <a href="https://www.w3.org/TR/vc-data-model/">latest Verifiable
Credentials Data Model</a>. The <a href="https://www.w3.org/TR/vc-data-model/#introduction">Introduction</a> and
<a href="https://www.w3.org/TR/vc-data-model/#terminology">Terminology</a> may be particularly helpful to W3C Members
seeking to better understand some the terminology used in this charter e.g., credentials vs. verifiable credentials and presentations vs. verifiable presentations.
seeking to better understand some the terminology used in this charter e.g., Credentials vs. Verifiable Credentials and Presentations vs. Verifiable Presentations.
</p>

<div class="noprint">
Expand Down Expand Up @@ -153,9 +153,9 @@ <h1 id="title"><i class="todo">PROPOSED</i> Verifiable Credentials Working Group
<h2>Scope</h2>
<p>
Building on the experience gained through implementation, deployment and usage
of verifiable credentials (VC), this Working Group will extend VC foundations with
new standardized technologies to improve the use of verifiable credentials on
the Web.
of Verifiable Credentials (VCs), this Working Group will extend Verifiable
Credential foundations with new standardized technologies to improve the use of
this technology on the Web.
</p>
<p>
The <b>scope</b> of the Verifiable Credentials Working Group is:
Expand All @@ -164,9 +164,9 @@ <h2>Scope</h2>
<li>Addressing errata, ambiguities, and interoperability problems found in previous versions of the Verifiable Credentials Data Model</li>
<li>A data model for Verifiable Credentials, inclusive of:</li>
<ul>
<li>credentials and verifiable credentials</li>
<li>presentations and verifiable presentations</li>
<li>requests for or submissions of verifiable credentials or verifiable presentations</li>
<li>Credentials and Verifiable Credentials</li>
<li>Presentations and Verifiable Presentations</li>
<li>requests for or submissions of Verifiable Credentials or Verifiable Presentations</li>
</ul>
<li>Registries for the data model</li>
<li>Algorithms for the expression and verification of proofs that use existing cryptographic primitives</li>
Expand All @@ -180,7 +180,7 @@ <h3 id="out-of-scope">Out of Scope</h3>
<p>The following features are <b>out of scope</b>, and will not be addressed by the Verifiable Credentials Working group:</p>

<ul class="out-of-scope">
<li>The mandate of any specific style of supporting infrastructure, such as a Distributed Ledger (DLT), for a verifiable credentials ecosystem</li>
<li>The mandate of any specific style of supporting infrastructure, such as a Distributed Ledger (DLT), for a Verifiable Credentials ecosystem</li>
<li>The specification of new cryptographic primitives</li>
<li>The normative specification of APIs or protocols</li>
</ul>
Expand Down Expand Up @@ -210,7 +210,7 @@ <h3>
<p>
This specification defines the Verifiable Credentials Data Model 2.0 along with
serializations of that data model. It will replace the current
<a href="https://www.w3.org/TR/vc-data-model/">VC Data Model 1.1 Recommendation</a>.
<a href="https://www.w3.org/TR/vc-data-model/">Verifiable Credentials Data Model 1.1 Recommendation</a>.
</p>

<p class="draft-status"><b>Draft state:</b> <a href="https://w3c.github.io/vc-data-model/">Editor's Draft</a> </p>
Expand All @@ -237,10 +237,10 @@ <h3>
<dd>
<p>
This family of specifications consists of documents that each define how to
express and associate proofs of integrity for verifiable credentials and
express and associate proofs of integrity for Verifiable Credentials and
concrete serializations for each of the defined syntaxes. The Working Group
would welcome the usage of these techniques for data in general, but
its scope will be to solve verifiable credentials use cases. The specific set of
its scope will be to solve Verifiable Credentials use cases. The specific set of
concrete serializations included will be determined by the Working Group. The
following are a non-exhaustive selection of expected input documents:
</p>
Expand Down Expand Up @@ -334,8 +334,8 @@ <h3>
including <a href="https://www.w3.org/2021/Process-20211102/#registry-definition">registry definitions</a>
and <a href="https://www.w3.org/2021/Process-20211102/#registry-table">registry tables</a>
to support extension points in the above normative deliverables. Registries for
extension points that are mandatory to use, for any of the above normative
deliverables (for example, Verifiable Credential properties that MUST be included in
extension points that are mandatory to use, for any of the above normative
deliverables (for example, Verifiable Credential properties that MUST be included in
a Verifiable Credential), must have at least one standardized entry.
</p>
</section>
Expand All @@ -356,17 +356,17 @@ <h3>
<li>Storage and Sharing of Verifiable Credentials</li>
<li>Privacy Guidance for Verifiable Credentials</li>
<li>Extensions for binding multilingual resources for localized user interfaces</li>
<li>A Developer Guide consisting of one or more notes related to general implementation guidance and best practices for working with VCs, including but not limited to:
<li>A Developer Guide consisting of one or more notes related to general implementation guidance and best practices for working with Verifiable Credentials, including but not limited to:
<ul>
<li>One or more HTTP protocol definitions for Verifiable Credential Exchange (such as the <a href="https://w3c-ccg.github.io/vc-api/">VC-API</a>)</li>
<li>Guidance on Verifiable Credential Exchange over <a href="https://openid.net/specs/openid-connect-core-1_0.html">OpenID Connect</a></li>
<li>Verifiable Credential Exchange over <a href="https://datatracker.ietf.org/doc/html/draft-ietf-gnap-core-protocol">Grant Negotiation and Authorization Protocol (GNAP)</a></li>
<li>Other protocols as time, attention, and resources permit.</li>
</ul>
</li>
<li>Guidance to enhance verifiable credential interoperability:
<li>Guidance to enhance Verifiable Credential interoperability:
<ul>
<li>VC Extension Vocabularies (e.g., ISO 18013-5 Mobile Driver's License)</li>
<li>Verifiable Credential Extension Vocabularies (e.g., ISO 18013-5 Mobile Driver's License)</li>
<li>Implementation Guides</li>
<li>Test Suites</li>
</ul>
Expand Down