Closed msporny closed 10 months ago
I read the call minutes at https://www.w3.org/2017/vc/WG/Meetings/Minutes/2023-10-18-vcwg. I object to saying that we've resolved the Controller Document issue in the manner described. We don't need an issue marker - which won't resolve it. We need a separate Controller Document specification that is normatively referenced by both securing specifications.
This is tracked in https://github.com/w3c/vc-data-model/issues/1307, which is a "before CR" issue. This is a tracked in VC-JOSE-COSE at https://github.com/w3c/vc-jose-cose/issues/160.
Please change the title of this issue to "Create and reference Controller Document specification" and update the issue description accordingly.
Please change the title of this issue to "Create and reference Controller Document specification" and update the issue description accordingly.
We discussed that path forward during the call and there were objections to proceeding in that manner. The publication of a Controller Document specification is fraught given the WG timeline and the suggestion that there would be breaking changes. We would need to go through a full FPWD -> WD -> CR and IPR cycle, including a 3-month horizontal review, which (if we started now) would put us entering CR 3 months before the end of our charter.
The path proposed was to proceed in parallel; make an attempt at a unified Controller Document specification, and if that succeeded (and only if it succeeded to progress to CR), reference that new specification from the securing specifications. Tying all of these specifications together in the manner you propose was something that multiple members in the WG disagreed with, and I would expect such a proposal to fail to achieve consensus.
PR #219 has been raised to address this issue. This issue will be closed once PR #219 is merged.
The issue was discussed in a meeting on 2023-10-24
List of resolutions:
The issue was discussed in a meeting on 2023-10-25
List of resolutions:
PR #219 has been merged, closing.
As discussed during the telecon today, the WG decided to add a note outlining a desired convergence w/ controller documents across securing mechanisms, and if successful, the referencing of that potential future document by the Data Integrity specification (if an only if that other document achieves WG consensus).