From c2466a24df0cfb2abc517ad5fa978d65a038e980 Mon Sep 17 00:00:00 2001
From: Manu Sporny Issuer
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 [[?VC-CONTROLLER-DOCUMENT]] about the
-[=issuer=] that can be used to [=verify=] the information expressed in
-the [=credential=].
+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=].
@@ -4000,11 +4000,13 @@ Securing Mechanism Specifications
Securing Mechanism Specifications
+ title="Choice of securing mechanism is use-case dependent"> There are multiple acceptable securing mechanisms, and this specification does not mandate any particular securing mechanism for use with [=verifiable credentials=] or [=verifiable presentations=]. @@ -4036,6 +4038,17 @@
+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. +
+