Hi, while updating my client implementation I noted that there seems to be an arbitrary mix in object key naming conventions:
camelCase - newKey - keyAuthorization - notBefore - notAfter kebab-case - (all directory fields) - terms-of-service-agreed - only-return-existing - external-account-binding In my opinion this makes the mapping of JSON objects to implementation language objects/types unnecessarily complicated. I don't know if it is to late to do something about that. Best, Sophie _______________________________________________ Acme mailing list [email protected] https://www.ietf.org/mailman/listinfo/acme
