So this has been an interesting one I have been chipping away at
How can we represent the ACME protocol as a Swagger Doc.
The key challenge seems to be the use of JWS where the "model" would be at JWS token. I.e. the same thing over and over again.
{
"protected": base64url({
"alg": "ES256",
"kid": "https://example.com/acme/acct/evOfKhNU60wg",
"nonce": "ax5RnthDqp_Yf4_HZnFLmA",
"url": "https://example.com/acme/acct/evOfKhNU60wg"
}),
"payload": base64url({
"contact": [
"mailto:certificates@example.org",
"mailto:admin@example.org"
]
}),
"signature": "hDXzvcj8T6fbFbmn...rDzXzzvzpRy64N0o"
}
Humans are too great at reading base64 payloads.
So my though is to create a OAS3 models for each payload and references it in the documents.
The responses are pretty well defined so are easy to represent.
The key question is would that provide value and should we try to pursue this?
The quick look around the forums suggests it's in the too hard basket?