diff --git a/index.html b/index.html
index 31bfb4b..a7a45ca 100644
--- a/index.html
+++ b/index.html
@@ -32,11 +32,11 @@
// extend the bibliography entries
localBiblio: ccg.localBiblio,
- github: "https://github.com/w3c-ccg/did-resolution",
+ github: "https://github.com/w3c/did-resolution",
includePermalinks: false,
// if there a publicly available Editor's Draft, this is the link
- edDraftURI: "https://w3c-ccg.github.io/did-resolution/",
+ edDraftURI: "https://w3c.github.io/did-resolution/",
// if this is a LCWD, uncomment and set the end of its review period
// lcEnd: "2009-08-05",
@@ -105,7 +105,7 @@
Comments regarding this document are welcome. Please file issues
- directly on GitHub,
+ directly on GitHub,
or send them to
public-credentials@w3.org
(subscribe,
@@ -150,7 +150,7 @@ The difference between "resolving" a DID and "dereferencing" a DID URL
is being thoroughly discussed by the community. For example, see
- this comment.Introduction
Should we define functionality that enables discovery of the list of DID methods or other capabilities that are supported by a DID resolver? Or is this implementation-specific and out-of-scope - for this spec? For example, see here and - here.
+ for this spec? For example, see here and + here.As an example, mention what it means to "resolve" DIDs that are simply wrapped public keys (for instance, see [[DID-KEY]] and - here).
+ here).Depending on the exact nature of the DID method's "Read" operation, the interaction between a DID resolver and the verifiable data registry may be implemented as a verifiable read @@ -722,7 +722,7 @@
Also describe mitigations against potential downsides of remote bindings, e.g.:
An advanced idea is that the result of DID resolution could be contextual or depend on policies, - see this comment.
+ see this comment.A related topic is whether (parts of) DID document could be encrypted, e.g., @@ -1541,7 +1541,7 @@