/Docs/G/Kantara-UMA-Text-CmA/Terminology/0.md
Document views: Document Xray Visual Cicero Print   Source views: Source JSON(ish)   On GitHub: File ~PageRank   (rare: 'ShowMe' 1)
Title: Terminology

Text:
  1. Terms
    This framework uses the following terms. Where terms are used without capitalization and are not otherwise defined in the [UMAcore], they are used in their normal sense.
    {Individual}
    A natural person (that is, a human being) with the capacity to take on contractual duties and obligations as a participant in an {UMA} interaction.
    {Legal_Person}
    A legal entity to which the law ascribes the ability to contract, such as a corporation, partnership, agency or government.
    {Person}
    An {Individual} or {Legal_Person}. {Persons} play various roles in achieving and seeking user-managed access, and the same {Person} might serve in multiple contractual roles.
    {Conformance}
    Claimed adherence of a running software program or service to the requirements of one or more of the roles "authorization server", "resource server", or "client", as defined in [UMAcore]. Software components play various roles in participating in the technical interactions necessary to achieve and seek user-managed access, and the same software component might serve in multiple technical roles.
    {Resource_Subject}
    The {Person} to whom a digital data resource relates.
    {Grantor}
    The {Person} who manages access to a digital data resource, either as its {Resource_Subject} or on that {Person}'s behalf.
    {Authorization_Server}
    A software service that fills the "authorization server" role as defined in [UMAcore].
    {Authorization_Server_Operator}
    A {Person} responsible for running and operating an {Authorization_Server}.
    {Resource_Server}
    A software service that fills the "resource server" role as defined in [UMAcore].
    {Resource_Server_Operator}
    A {Person} responsible for running and operating a {Resource_Server}.
    {Client}
    A software application or service that fills the "client" role as defined in [UMAcore].
    {Client_Operator}
    A {Person} responsible for running and operating a {Client}.
    {Requesting_Party}
    A {Person} that uses a {Client} to seek access to a protected resource. This {Person} may be an {Individual} or an {Legal_Person}. The {Requesting_Party} and the {Grantor} may be the same {Person} or different {Persons}.
    {Requesting_Party_Agent}
    A {Person} using a {Client} to seek access to a protected resource on behalf of a {Requesting_Party}. Typically this {Person} is an {Individual} acting on behalf of an {Legal_Person}.
  2. Abbreviations
    This framework uses the following abbreviations.
    {UMA}
    User-Managed Access, the interoperability protocol defined by in [UMAcore] and the other specifications it includes normatively by reference.
    {API}
    Application programming interface.
    {PAT}
    Protection {API} token, as defined in [UMAcore].
    {AAT}
    Authorization {API} token, as defined in [UMAcore].
    {RPT}
    Requesting party token, as defined in [UMAcore].


Comments: None Signaled