We're in agreement that JOSE could have been much simpler. Again, I'm not a fan of JOSE, but I definitely see a gaping need for something like it. Defining the

We're in agreement that JOSE could have been much simpler. Again, I'm not a fan of JOSE, but I definitely see a gaping need for something like it. Defining the "however you like" parts is the chief role of something like JOSE. Cryptographic standards like Ed25519 or ECDSA are not messaging formats. There needs to be an agreed way to send messages. That's the point of JOSE. > so you need an actual written standard for how to shove the signed data and the signature into a single [...] you could just encode a tuple of (data, signature) [...] Need the header to encode which key to use to verify it? Fine, add a description of the key to the tuple [...] Need algorithm agility? Fine, treat the algorithm as part of the public key. That's what JOSE defines.