Bob,
Your response to Steve Dusse ends with examples of potential
CAs and the awkwardness of the name subordination requirement in these
circumstances. I think that either you are creating examples of
authorization certificates or of entities who should be PCAs vs. CAs.
I tend to think of credit cards that I have as identifying me
in a descriptive context that is NOT useful for interpersonal email of
even inter-corporate email, EDI, etc. The credit cards essentially
name me not as a resident, or an employee, but as a holder of that
card (ultimately identified by a 13-16 didgt number). Thus, if these
organization issued me certificates, I would not be surprized to see
me identified under a DN arc that included the term "cardholder" (of
course, my amex cards woukd call me a "member"). Similarly, if ACM
identified me, it might be as a voting member (e.g., vs. student
member or employee of ACM), the same term that appears on my ACM
membership card.
If these organizations really want to identify other
organizations in a broader context, not based on the sorts of
affiliatioons noted above, they could do so in the role of PCAs.
Having PCAs serving different industries is not my ideal case, but if
the PCA policy included certain rules about financial liability and
other things especially relevant to that industry or trade
association, then maybe that's the best way to establish a PCA that
asserts what you want!
Steve