Update controller document reference.

index.html

@@ -188,7 +188,7 @@
  companyURL: "https://www.transmute.industries/",
  note: "v2.0", w3cid: 109171}
  ],
- xref: ["URL", "I18N-GLOSSARY", "INFRA"],
+ xref: ["URL", "I18N-GLOSSARY", "INFRA", "CONTROLLER-DOCUMENT"],
  lint: { "informative-dfn": false },
  maxTocLevel: 3,
  inlineCSS: true
@@ -1859,10 +1859,10 @@ <h3>Issuer</h3>
 [=URL=], or an object containing an `id` [=property=]
 whose value is a [=URL=]; in either case, the issuer selects this
 [=URL=] to identify itself in a globally unambiguous
-way. It is RECOMMENDED that the [=URL=] be one which, if dereferenced,
-results in a controller document, as defined in [[VC-DATA-INTEGRITY]] or
-[[VC-JOSE-COSE]], about the [=issuer=] that can be used to [=verify=] the
-information expressed in the [=credential=].
+way. It is RECOMMENDED that the [=URL=] be one which, if dereferenced, results
+in a controller document, as defined in [[CONTROLLER-DOCUMENT]], about the
+[=issuer=] that can be used to [=verify=] the information expressed in the
+[=credential=].
  </dd>
  </dl>
 
@@ -4160,17 +4160,6 @@ <h3>Securing Mechanism Specifications</h3>
  </dd>
  </dl>
 
- <p class="issue atrisk"
- title="Controller document reference might change">
-The Working Group is currently attempting to align the definitions of a
-controller document between [[[?DID-CORE]]], [[[?VC-DATA-INTEGRITY]]], and
-[[[?VC-JOSE-COSE]]]. The goal is to have one specification that each of the
-previously stated specifications, and this specification, can reference for
-the normative statements related to controller documents. The normative
-references to controller documents are expected to change during the
-Candidate Recommendation phase.
- </p>
-
  <p>
 Securing mechanism specifications SHOULD provide integrity protection for any
 information referenced by a URL that is critical to validation. Mechanisms that