Darn, revised complete list as I missed some:

authorization process (new)
authorization interface (new)
authorization API (obsolete)
UMA grant (new)
trust elevation (still used but some not crazy about it)
gathered claims, claims gathering (intended to be used just for interactive)
requesting party claims endpoint (original, sometimes accidentally subbed with "interactive claims-gathering endpoint")
pushed claims, claim pushing
claims collection (sort of new, intended to be used for both interactive and pushed)
authorization data (generic original term for profitable data associated with RPT, concept used throughout)
permissions (specific original term for resource set IDs + scopes (authorization data) associated with RPT)
scopes (similar to OAuth notion of scopes with an imprecise amount of conceptual delta)

Eve Maler
Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl

On Tue, Nov 1, 2016 at 6:03 PM, Eve Maler <eve@xmlgrrl.com> wrote:

https://github.com/KantaraInitiative/wg-uma/issues/256

This is one of a series of messages meant for discussion of naming of entities and concepts. This message consolidates a bunch of authorization/claims terms from the GitHub issue:
authorization process (new)
authorization interface (new)
authorization API (obsolete)
UMA grant (new)
trust elevation (still used but some not crazy about it)
gathered claims, claims gathering (intended to be used just for interactive)
requesting party claims endpoint (original, sometimes accidentally subbed with "interactive claims-gathering endpoint")
pushed claims, claim pushing
claims collection (sort of new, intended to be used for both interactive and pushed)
For now, let's please discuss only in email, unless we're all somehow magically aligned by the time we get to the next call. I'll provide my own thoughts in a followup message.

Eve Maler
Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl