Let me put it a different way: Offering the same value in multiple places is really bad API design. I'm trying to fix that. We could remove the inlined authorization status, leaving the requirements with an inline status. But while we're at it, why not give requirements their own addressable URLs? And what, fundamentally, is different about requirements vs authorizations?
_______________________________________________ Acme mailing list [email protected] https://www.ietf.org/mailman/listinfo/acme
