Remove issue marker about SRI that is no longer relevant.

index.html

@@ -3313,7 +3313,7 @@ <h2>Integrity of Related Resources</h2>
         <p>
 Any object in the [=verifiable credential=] that contains an `id`
 property MAY be annotated with integrity information by adding either the
-`digestSRI` or `digestMultibase` property, either of which MAY be 
+`digestSRI` or `digestMultibase` property, either of which MAY be
 accompanied by the additionally optional `mediaType` property.
         </p>
 
@@ -3338,15 +3338,6 @@ <h2>Integrity of Related Resources</h2>
 choosing a current and reliable hash algorithm. At the time of this writing
 `sha384` SHOULD be considered the minimum strength hash algorithm for use by
 implementers.
-        </p>
-        <p class="issue">
-The working group is discussing if we will adopt more aspects of subresource
-integrity as defined in [[SRI]] is adopted into the [[JSON-LD11]] specification as
-noted in that specifications <a href="https://www.w3.org/TR/json-ld11/#security">
-current security considerations</a> of that specification, the
-approach described in this section can serve as an additional check towards
-ensuring that a cached context used when issuing
-a [=verifiable credential=] matches the remote resource.
         </p>
         <p>
 An example of a related resource integrity object referencing JSON-LD contexts.