working on #777

README.md

@@ -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.

index.html

@@ -827,21 +827,21 @@ <h3>Presentations</h3>
 <a>verifiable presentation</a>, but abstracts the details about how
 <a>verifiable credentials</a> are organized into information <a>graphs</a>,
 which are then organized into <a>verifiable presentations</a>.
+        </p>
+        <p>
 <a href="#info-graph-vp"></a> below shows a more complete depiction of a
 <a>verifiable presentation</a>, which is normally composed of at least four
-information <a>graphs</a>. The first <a>graph</a> expresses the
-<a>verifiable presentation</a> itself, which contains
-<span class="color-text" style="color:#b4a7d6;">presentation metadata</span>.
-The <code>verifiableCredential</code> property in the <a>graph</a> refers to
-one or more <a>verifiable credentials</a> (each a self-contained <a>graph</a>),
-which in turn contains
-<span class="color-text" style="color:#d5a6bd;">credential metadata</span> and
-<span class="color-text" style="color:#ffe599;">claims</span>.
-The third <a>graph</a> expresses the
-<span class="color-text" style="color:#b6d7a8;">credential graph proof</span>,
-which is usually a digital signature. The fourth <a>graph</a> expresses the
-<span class="color-text" style="color:#a4c2f4;">presentation graph proof</span>,
-which is usually a digital signature.
+information <a>graphs</a>. The first of these <a>graphs</a>, the Presentation
+<a>Graph</a>, expresses the <a>verifiable presentation</a> itself, which
+contains presentation metadata. The <code>verifiableCredential</code>
+property in the Presentation <a>Graph</a> refers to one or more <a>verifiable
+credentials</a>, each being one of the second information <a>graphs</a>, i.e.,
+a self-contained Credential <a>Graph</a>), which in turn contains credential
+metadata and claims. The third information <a>graph</a>, the Credential Proof
+<a>Graph</a>, expresses the credential graph proof, which is usually a digital
+signature. The fourth information <a>graph</a>, the Presentation Proof
+<a>Graph</a>, expresses the presentation graph proof, which is usually a
+digital signature.
         </p>
 
         <figure id="info-graph-vp">