Examples in this section show headers 0xed01 and 0x8026 being used but does not provide any references to where these values originate or how to represent anything other than an ed25519 public or private key. It is implied that these values originate from Multicodec but, given that Multicodec is not considered a standard, I assume we would want to adopt at least a subset of the codes defined there.
As it stands, the Multikey section can be confusing given this omission and perpetuates a conflation between Multibase encoding and Multicodec binary data headers.
Referencing this section: https://www.w3.org/TR/vc-data-integrity/#multikey
Examples in this section show headers
0xed01
and0x8026
being used but does not provide any references to where these values originate or how to represent anything other than an ed25519 public or private key. It is implied that these values originate from Multicodec but, given that Multicodec is not considered a standard, I assume we would want to adopt at least a subset of the codes defined there.As it stands, the Multikey section can be confusing given this omission and perpetuates a conflation between Multibase encoding and Multicodec binary data headers.