What is the "Other party" in Attribute Handling called?

[Tom Zeller]

> My suggestion at the meeting was to look at something identifying the specific recipient of the results of the attribute resolution, so perhaps something called AttributeRecipientContext.

And the AttributeRecipientContext would provide getId(), that is what
you were thinking ?

> A multiple-recipient use case might execute multiple webflows with the resolver, setting the attribute recipient different each time. Or something more optimized by changing the resolver to understand a multiple recipient context, but either way, the "requester" or "relying party" don't enter into it.

I like the multiple recipient context idea, something like
getRecipients() on the AttributeRecipientContext, to make it efficient
for the attribute resolver to resolve shared attributes. But that
seems like further stepping away from v2, and I'm not sure how far we
want to go in that direction.