Closed msporny closed 3 months ago
Looking back at the previous comments, my vote would be for @TallTed's formulation in https://github.com/w3c/vc-data-integrity/pull/292#discussion_r1686902419.
I am not saying we should (it is probably too late for that anyway) but I want to be sure that we are all aware of this fact.
Yes, it's a good point, though without an alternative I hesitate to try and create language that would be inclusive of that alternative. I did make a pass to try to figure out how else to say it, and it's difficult to say it w/o also pointing to the alternative.
Ultimately, this language is in the Algorithms section and that applies directly to DI and its usage of proof
. I'm not sure we need to be concerned w/ other specifications and their "proof" values, because DI proofs have nothing to do with those other securing mechanisms (we don't have language on how to process those other things... we only know of our own properties and algorithms).
Editorial, multiple reviews, changes requested and made, no objections, merging.
This PR is an attempt to address issue #287 by clarifying the meaning of unsecured/secured document..
Preview | Diff