The one downside for this naming pattern is the number of characters that are used (around of 15 characters) and how they interact w/ semantic compression mechanisms like CBOR-LD (badly, not easy to compress non-repeating text strings). This is a problem for small payload sizes, such as VCs sent over NFC and QR Codes, where the byte payload has to stay under around 395 bytes for a QR Code payload to be read on an average retail optical scanner.
Adding a sec:cryptosuite datatype will allow us to compress the 15 characters down to single byte values for the cryptosuite type. This issue is to track adding the data type to the specification and the vocabulary.
It seems like we have consensus on the naming pattern that will be used for cryptosuites: https://github.com/w3c/vc-di-ecdsa/pull/23
The one downside for this naming pattern is the number of characters that are used (around of 15 characters) and how they interact w/ semantic compression mechanisms like CBOR-LD (badly, not easy to compress non-repeating text strings). This is a problem for small payload sizes, such as VCs sent over NFC and QR Codes, where the byte payload has to stay under around 395 bytes for a QR Code payload to be read on an average retail optical scanner.
Adding a
sec:cryptosuite
datatype will allow us to compress the 15 characters down to single byte values for the cryptosuite type. This issue is to track adding the data type to the specification and the vocabulary.