Skip to content

A moderate rework of the introductory text and images #56

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

Merged
merged 21 commits into from
Jul 22, 2017
Merged
Changes from all commits
Commits
Show all changes
21 commits
Select commit Hold shift + click to select a range
8d12008
Fix bad reference to IDENTITY_CREDENTIALS.
msporny Jun 10, 2017
e4f0d29
Fix reference to VC-USECASES.
msporny Jun 10, 2017
ba7ae2c
Fix duplicate definition of entity credential.
msporny Jun 10, 2017
4ff5afe
Fix misc ReSpec reference errors.
msporny Jun 10, 2017
52486ce
Make abstract less technically dense.
msporny Jun 10, 2017
222e8cd
Fix grammatical issues in status of the document section.
msporny Jun 10, 2017
035369e
Revise introduction, add ecosystem, data model overview.
msporny Jun 10, 2017
41e151c
Add intro section on verifiable claims.
msporny Jun 10, 2017
dcd7b60
Update issuer, holder, inspector, and identity registry terms.
msporny Jun 10, 2017
de7a78f
Add content for ecosystem overview section.
msporny Jun 10, 2017
6980b97
Make "expressing" section titles shorter.
msporny Jun 10, 2017
41da504
Update use cases and requirements section.
msporny Jun 10, 2017
551580a
Fix description of introductory sections.
msporny Jun 10, 2017
483a9fb
Update opening sentence to Abstract and Intro
stonematt Jun 14, 2017
b901e99
Update intro paragraph
stonematt Jun 15, 2017
f60efec
Updated Intro and Abstract language.
stonematt Jun 21, 2017
7994737
Update terminology - inspector -> verifier.
msporny Jul 6, 2017
5684d1b
Simplify abstract, clean up introductory paragraph.
msporny Jul 6, 2017
7b02dbb
Fix glossary terminology from inspector -> verifier.
msporny Jul 6, 2017
ae83ffb
Minor fixes to language in abstract.
msporny Jul 6, 2017
5b74883
Fix DID format to match latest format.
msporny Jul 6, 2017
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
20 changes: 10 additions & 10 deletions common.js
Original file line number Diff line number Diff line change
@@ -16,16 +16,16 @@ var vcwg = {
},
"VC-USECASES": {
title: "Verifiable Claims Use Cases",
href: "http://w3c.github.io/vc-use-cases/",
href: "https://www.w3.org/TR/verifiable-claims-use-cases/",
authors: [
"Shane McCarron",
"Daniel Burnett",
"Gregg Kellogg",
"Brian Sletten",
"Manu Sporny"
],
status: "IG-DRAFT",
publisher: "Web Payments Interest Group Verifiable Claims Task Force"
status: "FPWD",
publisher: "Verifiable Claims Working Group"
},
// aliases to known references
"HTTP-SIGNATURES": {
@@ -64,7 +64,7 @@ var vcwg = {
// referenced from the common definitions
//
// the termlist is in a block of class "termlist", so make sure that
// has an ID and put that ID into the termLists array so we can
// has an ID and put that ID into the termLists array so we can
// interrogate all of the included termlists later.
var termNames = [] ;
var termLists = [] ;
@@ -78,7 +78,7 @@ function restrictReferences(utils, content) {
// New new logic:
//
// 1. build a list of all term-internal references
// 2. When ready to process, for each reference INTO the terms,
// 2. When ready to process, for each reference INTO the terms,
// remove any terms they reference from the termNames array too.
$.each(base.querySelectorAll("dfn"), function(i, item) {
var $t = $(item) ;
@@ -92,7 +92,7 @@ function restrictReferences(utils, content) {
dropit = true;
}
});
}
}
// do we have an includeTerms
if (window.hasOwnProperty("includeTerms")) {
var found = false;
@@ -158,7 +158,7 @@ require(["core/pubsubhub"], function(respecEvents) {
}
}) ;

// clearRefs is recursive. Walk down the tree of
// clearRefs is recursive. Walk down the tree of
// references to ensure that all references are resolved.
var clearRefs = function(theTerm) {
if ( termsReferencedByTerms[theTerm] ) {
@@ -174,9 +174,9 @@ require(["core/pubsubhub"], function(respecEvents) {
delete termNames[theTerm];
}
};
// now termsReferencedByTerms has ALL terms that
// reference other terms, and a list of the

// now termsReferencedByTerms has ALL terms that
// reference other terms, and a list of the
// terms that they reference
$("a.internalDFN").each(function () {
var $item = $(this) ;
4 changes: 4 additions & 0 deletions diagrams/vc-ecosystem-overview.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
4 changes: 4 additions & 0 deletions diagrams/verifiable-claims.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
412 changes: 260 additions & 152 deletions index.html

Large diffs are not rendered by default.

39 changes: 21 additions & 18 deletions terms.html
Original file line number Diff line number Diff line change
@@ -6,10 +6,10 @@
</p>

<dl class="termlist">
<dt><dfn data-lt="verifiable claim|claims">claim</dfn></dt>
<dt><dfn data-lt="verifiable claim|verifiable claims|claims">claim</dfn></dt>
<dd>
A statement made by an <a>entity</a> about a <a>subject</a>. A
<a>verifiable claim</a> is a claim that is effectively tamper-proof and whose
<strong>verifiable claim</strong> is a claim that is effectively tamper-proof and whose
authorship can be cryptographically verified.
</dd>
<dt><dfn>credential curator</dfn></dt>
@@ -21,7 +21,7 @@
<dd>
A program, such as a <a>credential</a> storage vault or personal
credential wallet, that stores and protects access to a
<a>recipient's</a> credentials.
<a>holder's</a> credentials.
</dd>
<dt><dfn data-lt="CTP">credential transport protocol</dfn></dt>
<dd>
@@ -41,7 +41,7 @@
A portable URI-based identifier, also known as a DID, that is associated with
an <a>entity</a>. These
identifiers are most often used in a <a>credential</a> and are associated
with <a>recipients</a> such that the <a>credential</a> itself can be easily
with <a>holders</a> such that the <a>credential</a> itself can be easily
ported from one <a>identity provider</a> to another without the need to
reissue the <a>credential</a>. An example of a DID is:
<code>did:b6922d8e-20df-4939-95cd-f79375979178</code>
@@ -61,17 +61,16 @@
A thing with distinct and independent existence such as a person, organization,
concept, or device.
</dd>
<dt><dfn data-lt="credential|credentials|entity credential|entity credentials">entity credential</dfn></dt>
<dt><dfn data-lt="credential|credentials|entity credentials">entity credential</dfn></dt>
<dd>
A set of one or more claims made by the same <a>entity</a> about a
<a>subject</a>.
</dd>
<dt><dfn data-lt="holders|holder's|recipient|recipients|recipient's">holder</dfn></dt>
<dt><dfn data-lt="holders|holder's">holder</dfn></dt>
<dd>
An <a>entity</a> that is in control of a particular <a>credential</a>.
Typically a holder is also the primary subject of the information
in a credential. A holder is often the <a>entity</a> that initiates the
transmission of a credential.
An <a>entity</a> that is in control of one or more <a>verifiable claims</a>.
Typically a holder is also the primary <a>subject</a> of the
<a>verifiable claims</a> that they are holding.
</dd>
<dt><dfn data-lt="identities|identity's">identity</dfn></dt>
<dd>
@@ -80,10 +79,6 @@
digital contexts, typically using identifiers and attributes. Unintended
distribution or use of identity information can compromise privacy. Collection
and use of such information should follow the principles of minimal disclosure.
</dd>
<dt><dfn data-lt="inspector|inspectors|inspector's|credential inspectors|credential inspector's">inspector</dfn></dt>
<dd>
An <a>entity</a> that receives an <a>entity profile</a> for processing.
</dd>
<dt><dfn data-lt="entity documents">entity document</dfn></dt>
<dd>
@@ -101,18 +96,22 @@
associated <a>credentials</a> on behalf of an <a>entity</a>. It typically
handles requests to store <a>credentials</a> issued by an
<a>issuer</a> and to retrieve <a>credentials</a> when requested by a
<a>credential inspector</a>.
<a>verifier</a>.
</dd>
<dt><dfn data-lt="entity profile|entity profiles">entity profile</dfn></dt>
<dd>
A set of <a>entity credentials</a> related to the same <a>subject</a>.
An <a>entity</a> may have multiple entity profiles and each entity profile
may contain <a>claims</a> issued by multiple <a>entities</a>.
</dd>
<dt><dfn data-lt="identifier registries">identifier registry</dfn></dt>
<dd>
Mediates the creation and verification of <a>subject</a> identifiers.
</dd>
<dt><dfn data-lt="issuers|issuer's">issuer</dfn></dt>
<dd>
An <a>entity</a> that creates a <a>credential</a> and associates it
with a particular <a>holder</a>.
An <a>entity</a> that creates a <a>verifiable claim</a>, associates it
with a particular <a>subject</a>, and transmits it to a <a>holder</a>.
</dd>
<dt><dfn data-lt="subjects|subject's">subject</dfn></dt>
<dd>
@@ -123,6 +122,10 @@
<dd>
A program, such as a browser or other Web client, that mediates the
communication between <a>holders</a>, <a>issuers</a> and
<a>credential inspectors</a>.
<a>verifiers</a>.
</dd>
<dt><dfn data-lt="verifier|verifiers|verifier's|credential verifiers|credential verifier's">verifier</dfn></dt>
<dd>
An <a>entity</a> that receives one or more <a>verifiable claims</a> for processing.
</dd>
</dl>