Action event IDs for missing child contexts ?

[Tom Zeller]

>>I guess my question is : should we define an event id for every
>>context required in actions ?
>
> There were a lot in existence to start with, but I'm not one to advocate
> creating them because they represent code bugs, not runtime conditions.

Okay. So as a general rule, choose the closest/narrowest event id.

For reference, here are the event ids we have defined so far :

ACCOUNT_ERROR = "AccountError";
ACCOUNT_WARNING = "AccountWarning";
AUTHN_EXCEPTION = "AuthenticationException";
INVALID_ATTRIBUTE_CTX = "InvalidAttributeContext";
INVALID_AUTHN_CTX = "InvalidAuthenticationContext";
INVALID_CREDENTIALS = "InvalidCredentials";
INVALID_MESSAGE_VERSION = "InvalidMessageVersion";
INVALID_MSG_CTX = "InvalidMessageContext";
INVALID_MSG_MD = "InvalidMessageMetadata";
INVALID_NAMEID_POLICY = "InvalidNameIDPolicy";
INVALID_PROFILE_CONFIG = "InvalidProfileConfiguration";
INVALID_PROFILE_CTX = "InvalidProfileContext";
INVALID_RELYING_PARTY_CONFIG = "InvalidRelyingPartyConfiguration";
INVALID_RELYING_PARTY_CTX = "InvalidRelyingPartyContext";
INVALID_SUBJECT = "InvalidSubject";
INVALID_SUBJECT_C14N_CTX = "InvalidSubjectCanonicalizationContext";
INVALID_SUBJECT_CTX = "InvalidSubjectContext";
IO_ERROR = "InputOutputError";
NO_ASSERTION = "NoAssertion";
NO_CREDENTIALS = "NoCredentials";
NO_IN_MSG_ID = "NoInboundMessageId";
NO_POTENTIAL_FLOW = "NoPotentialFlow";
NO_RESPONSE = "NoResponse";
PROCEED_EVENT_ID = "proceed";
REQUEST_UNSUPPORTED = "RequestUnsupported";
RESELECT_FLOW = "ReselectFlow";
RESPONSE_EXISTS = "ResponseExists";
SUBJECT_C14N_ERROR = "SubjectCanonicalizationError";
UNABLE_ENCODE_ATTRIBUTE = "UnableToEncodeAttribute";
UNABLE_FILTER_ATTRIBS = "UnableToFilterAttributes";
UNABLE_RESOLVE_ATTRIBS = "UnableToResolveAttributes";
UNABLE_TO_DECODE = "UnableToDecode";
UNABLE_TO_ENCODE = "UnableToEncode";