TAG Review: Add examples of how to use DID resolution to solve the end-users' problems (#207)

* add design goals section

* Update index.html

Co-authored-by: Will Abramson <[email protected]>

* Update index.html

Co-authored-by: Will Abramson <[email protected]>

* Update index.html

Co-authored-by: Will Abramson <[email protected]>

* Update index.html

Co-authored-by: Will Abramson <[email protected]>

* Update index.html

Co-authored-by: Will Abramson <[email protected]>

* Update index.html

Co-authored-by: Ted Thibodeau Jr <[email protected]>

* Update index.html

Co-authored-by: Ted Thibodeau Jr <[email protected]>

* Update index.html

Co-authored-by: Ted Thibodeau Jr <[email protected]>

* Update index.html

Co-authored-by: Ted Thibodeau Jr <[email protected]>

* Update index.html

Co-authored-by: Ted Thibodeau Jr <[email protected]>

* Update index.html

Co-authored-by: Ted Thibodeau Jr <[email protected]>

* Update index.html

Co-authored-by: Will Abramson <[email protected]>

---------

Co-authored-by: Will Abramson <[email protected]>
Co-authored-by: Ted Thibodeau Jr <[email protected]>

Author: 3 people

index.html

@@ -192,6 +192,33 @@ <h1>Introduction</h1>
 	is being thoroughly discussed by the community. For example, see
 	<a href="https://github.com/w3c/did-spec/issues/166#issuecomment-464502719">this comment</a>.</p>
 
+	<section id="design-goals" class="informative">
+		<h2>Implementer Overview</h2>
+		<p>
+			By invoking a <a>DID resolver</a> using the standard <code>resolve(did, resolutionOptions)</code> interface (as defined in 
+			the <a href="#resolving">DID Resolution section</a>) one can obtain a <a>DID document</a> and accompanying metadata 
+			(e.g., `contentType`, proof, versioning) which an application can use to validate a user's cryptographic keys, 
+			service endpoints, or status. 
+		<p>
+			For example, a wallet app could resolve <code>did:example:123?versionTime=2021-05-10T17:00:00Z</code> 
+			using the `versionTime` parameter to retrieve the state of that DID at a past time, or a client could 
+			dereference a DID URL 
+			 like <code>did:example:123?service=files&relativeRef=/resume.pdf</code> 
+			 (see <a href="#example-dereferencing-to-service-endpoint-url">here for detailed example</a>) 
+			 to fetch a user's resume stored via a service declared in the DID document. 
+		</p>
+		<p>
+			Further, the specification's <a href="#dereferencing-algorithm">DID URL dereferencing algorithm</a> shows how 
+			a client can follow a fragment (e.g., <code>#key-1</code>) to extract a particular verification method from 
+			the <a>DID document</a> (see <a href="#example-dereferencing-to-verification-method">here for detailed example</a>). 
+			In practice, implementers validate their resolver against the 
+			<a href="https://github.com/w3c-ccg/did-resolution-test-suite">DID Resolution Test Suite</a> which exercises 
+			normative MUSTs and error conditions (such as invalid DIDs, deactivated DIDs, unsupported methods, 
+			relative URL expansion, etc.) to ensure that client applications can reliably depend on correct resolution behavior 
+			across different DID methods.
+		</p>
+	</section>
+
 	<section id="conformance">
 
 		<p>