Change JCS bibref to RFC8785, as it's now published.

Note that we discuss changing our canonicalization requirements to JCS when it becomes available, which it is now. Perhaps something to take up post-publication.

Author: gkellogg

common/jsonld.js

@@ -59,11 +59,11 @@ const jsonld = {
       status: 'unofficial',
       date: '29 May 2015'
     },
-    "JCS": {
+    "RFC8785": {
       title: "JSON Canonicalization Scheme (JCS)",
-      href: 'https://tools.ietf.org/html/draft-rundgren-json-canonicalization-scheme-17',
+      href: 'https://www.rfc-editor.org/rfc/rfc8785',
       authors: ['A. Rundgren', 'B. Jordan', 'S. Erdtman'],
-      publisher: 'Network Working Group',
+      publisher: 'Informational',
       status: 'Internet-Draft',
       date: '20 January 2020'
     },

index.html

@@ -4973,9 +4973,8 @@ <h3>Algorithm</h3>
           convert <var>value</var> to the <a>canonical lexical form</a>
           using the result of transforming the <a>internal representation</a> of <var>value</var>
           to JSON and set <var>datatype</var> to <code>rdf:JSON</code>.
-          <div class="issue">The JSON Canonicalization Scheme [[?JCS]]
-            is an emerging standard for JSON canonicalization
-            not yet ready to be referenced.
+          <div class="issue">The JSON Canonicalization Scheme (JCS) [[?RFC8785]]
+            is a standard for JSON canonicalization.
             When a JSON canonicalization standard becomes available,
             this specification will likely be updated to require such a canonical representation.
             Users are cautioned from depending on the