Remove at risk issue marker for refreshService property.

index.html

@@ -3378,15 +3378,6 @@ <h2>Integrity of Related Resources</h2>
       <section>
         <h3>Refreshing</h3>
 
-        <p class="issue atrisk" data-number="1437" title="Feature depends on demonstration of independent implementations">
-This feature is at risk and will be removed from the specification if at least
-two independent, interoperable implementations are not demonstrated for a
-single extension type by the end of the Candidate Recommendation Phase. If
-this feature is removed, the property will be included in Section
-<a href="#reserved-extension-points"></a>, in anticipation of future
-implementation and inclusion in the specification.
-        </p>
-
         <p>
 It is useful for systems to enable the manual or automatic refresh of an expired
 [=verifiable credential=]. For more information about validity periods for
@@ -3413,14 +3404,6 @@ <h3>Refreshing</h3>
 that does not contain public information or whose refresh service is not
 protected in some way.
         </p>
-        <p class="note"
-           title="Non-authenticated credential refresh">
-Placing a `refreshService` [=property=] in a
-[=verifiable credential=] so that it is available to [=verifiers=] can
-remove control and consent from the [=holder=] and allow the
-[=verifiable credential=] to be issued directly to the [=verifier=],
-thereby bypassing the [=holder=].
-        </p>
 
         <dl>
           <dt><var id="defn-refreshService">refreshService</var></dt>
@@ -3438,34 +3421,40 @@ <h3>Refreshing</h3>
           title="Usage of the refreshService property by an issuer">
 {
   "@context": [
-    "https://www.w3.org/ns/credentials/v2",
-    "https://www.w3.org/ns/credentials/examples/v2",
-    "https://w3id.org/vc-refresh-service/v1"
+    "https://www.w3.org/2018/credentials/v1",
+    "https://w3id.org/age/v1",
+    "https://w3id.org/security/suites/ed25519-2020/v1"
   ],
-  "id": "http://university.example/credentials/3732",
-  "type": ["VerifiableCredential", "ExampleDegreeCredential"],
-  "issuer": "https://university.example/issuers/14",
-  "validFrom": "2020-01-01T19:23:24Z",
+  "type": ["VerifiableCredential", "AgeVerificationCredential"],
+  "issuer": "did:key:z6MksFxi8wnHkNq4zgEskSZF45SuWQ4HndWSAVYRRGe9qDks",
+  "issuanceDate": "2024-04-03T00:00:00.000Z",
+  "expirationDate": "2024-12-15T00:00:00.000Z",
+  "name": "Age Verification Credential",
   "credentialSubject": {
-    "id": "did:example:ebfeb1f712ebc6f1c276e12ec21",
-    "degree": {
-      "type": "ExampleBachelorDegree",
-      "name": "Bachelor of Science and Arts"
-    }
+    "overAge": 21
   },
   <span class="highlight">"refreshService": {
     "type": "VerifiableCredentialRefreshService2021",
-    "url": "https://university.example/workflows/refresh-degree",
-    "validFrom": "2021-09-01T19:23:24Z",
-    "validUntil": "2022-02-01T19:23:24Z"
+    "url": "https://registration.provider.example/flows/reissue-age-token",
+    "refreshToken": "z2BJYfNtmWRiouWhDrbDQmC2zicUPBxsPg"
   }</span>
 }
         </pre>
 
         <p>
 In the example above, the [=issuer=] specifies an automatic
-`refreshService` that can be used by directing the [=holder=] to
-`https://university.example/workflows/refresh-degree`.
+`refreshService` that can be used by POSTing the [=verifiable credential=] to
+the refresh service `url`. Note that this particular verifiable credential is
+not intended to be shared with anyone except for the original issuer.
+        </p>
+
+        <p class="note"
+           title="Non-authenticated credential refresh">
+Placing a `refreshService` [=property=] in a
+[=verifiable credential=] so that it is available to [=verifiers=] can
+remove control and consent from the [=holder=] and allow the
+[=verifiable credential=] to be issued directly to the [=verifier=],
+thereby bypassing the [=holder=].
         </p>
 
       </section>
@@ -4184,7 +4173,7 @@ <h3>Securing Mechanism Specifications</h3>
         <p>
 A securing mechanism specification that creates a new type of [=embedded proof=]
 MUST specify a [=property=] that relates the [=verifiable credential=] or [=verifiable
-presentation=] to a [=proof graph=]. 
+presentation=] to a [=proof graph=].
 The requirements on the securing mechanism are as follow:
         </p>
         <ul>
@@ -4195,15 +4184,15 @@ <h3>Securing Mechanism Specifications</h3>
           </li>
           <li>
 The securing mechanism MUST secure all graphs in the [=verifiable credential=] or the [=verifiable
-presentation=], except for any [=proof graphs=] securing the [=verifiable credential=] 
+presentation=], except for any [=proof graphs=] securing the [=verifiable credential=]
 or the [=verifiable presentation=] itself.
           </li>
 
         </ul>
 
       <p class="note">
-The last requirement means that the securing mechanism secures the [=default graph=] and, 
-for [=verifiable presentations=], each [=verifiable credential=] of the presentation, together with 
+The last requirement means that the securing mechanism secures the [=default graph=] and,
+for [=verifiable presentations=], each [=verifiable credential=] of the presentation, together with
 their respective [=proof graphs=].
 See also <a href="#info-graph-vp"></a> or <a href="#info-graph-vp-mult-creds"></a>.
       </p>
@@ -6789,7 +6778,7 @@ <h3>"Artificial Intelligence" and "Machine Learning"</h3>
 Systems using what is today commonly referred to as "artificial intelligence" and/or "machine learning" might be capable of performing
 complex tasks at a level that meets or exceeds human performance.
 This might include tasks such as the acquisition and use of
-[=verifiable credentials=]. 
+[=verifiable credentials=].
 Using such tasks to distinguish between human and automated "bot" activity, as is
 commonly done today with a <a href="https://en.wikipedia.org/wiki/CAPTCHA">CAPTCHA</a>,
 for instance, might thereby cease to provide adequate or acceptable protection.
@@ -7025,10 +7014,6 @@ <h3>Vocabularies</h3>
               <td>
 Serves as a superclass for specific refresh service types that are placed into
 the <a href="#refreshing">credentialRefresh</a> property.
-<span class="issue atrisk">This superclass is at risk and will be removed if
-at least two independent implementations for the superclass are not identified
-by the end of the Candidate Recommendation phase.
-</span>
               </td>
             </tr>
             <tr id="bc-render-method">