Dave Huseby
Dave Huseby
The new Multisig and Multikey specs and implementations strictly follow: * They MUST be in-band (with the value); not out-of-band (in context). * They MUST avoid lock-in and promote extensibility....
@rvagg > If decoding bytes using this codec doesn't yield any "links" (concretely: CIDs), such that it can contribute to a larger graph, then serialization may be a better choice....
Thank you for taking time to review this. I changed the provenance-log and provenance-log-entry to be `serialization`. I changed a VLAD from `cid` to `vlad` since it is an identifier...
I also just corrected the `es384-msig` name error. I filed an issue for the same name error for varsig: #348
Also just cleaned up the `es521-msig` name error. I filed an issue for the same name error for varsig: #349
> So if you would move your additions to a 2 bytes or higher section, that would be great. I can do that, but what about the `multikey`, `multisig`, `nonce`,...
My multikey predates the W3C use. There's no mention of multikey in this file yet. Plus the verifiable credentials spec has failed to gain adoption in key political and business...
> including single-entry ones: vlag, nonce, multikey At the risk of bikeshedding... vlad and cid tags should just be "identifier" or something generic like that. multikey and key could be...
Thanks! Can we land this?
I think all concerns have been addressed.