Merge pull request #650 from w3c-ccg/641-service-section-outdated

feat: service section update

docs/spec/sections/use-case-requirements.html

@@ -89,7 +89,7 @@ <h5>Discovering Organizational Identifiers</h5>
 </pre>
 
  <p>
-2. Review the <code>serviceEndpoint</code>, <code>assertionMethod</code>, and <code>authentication</code> sections of the DID document.
+2. Review the <code>serviceEndpoint</code>, and <code>assertionMethod</code> sections of the DID document.
  </p>
 <section>
   <h5>service</h5>
@@ -107,7 +107,7 @@ <h5>service</h5>
 This entry MUST be present.
 </p>
 <p>
-This entry MUST have an element of type <code>TraceabilityAPI</code> with a <code>serviceEndpoint</code> URL for a VC-API that supports presentation exchange.
+This entry MUST have an element of type <code>TraceabilityAPI</code> with a <code>serviceEndpoint</code> URL for an endpoint which supports presentation exchange.
 </p>
 
   <p>For example:</p>
@@ -122,24 +122,15 @@ <h5>service</h5>
 ]
 </pre>
 
-<p>This definition implies the following endpoints:</p>
+<p>This definition implies that a <code>/presentations</code> endpoint is available for data submissions:</p>
 
 <pre class="example">
-https://platform.example/organization/123/credentials/issue
-https://platform.example/organization/123/credentials/verify
 https://platform.example/organization/123/presentations
 </pre>
 
 <p>
-These endpoints always require the application to be authenticated:
-</p>
+This endpoint must be secured as defined in <a href="./#authorization">Authentication</a>.
 
-<pre class="example">
-https://platform.example/organization/123/credentials/issue
-</pre>
-
-<p class="advisement">
-Implementations are encouraged to require authentication for all endpoints.
 </p>
 
 </section>