Abstract: This document records the scenarios and use cases governing the development of the User-Managed Access protocol and guiding associated implementations and deployments.

Version: See the Change History at the end of this document for its revision number.

Intellectual property rights: The User-Managed Access Work Group operates under Option Liberty and the publication of this document is governed by the policies outlined in this option.

You can find a template for scenarios and subordinate use cases at the end of this document. Change the status of each scenario and use case appropriately in its title string, indicating below the meeting date when the decision was made:

• pending: its status when first submitted and until its disposition is decided
• accepted: accepted to be solved in UMA V1 and its associated compliant applications and implementations
• deferred: likely in the correct problem space but deferred for later consideration in future versions
• rejected: not considered to be in the UMA problem space

Pending Scenario: Sharing a Single Resource with a Vendor

Submitted by: Eve Maler
Status as of: date

(Provide description of the scenario with all nontechnical particulars, noting requirements, constraints, and other observations. Avoid diagrams.)

Use Case: Separate Resource Host, Relationship Manager, and Recipient

Submitted by: Eve Maler
Status: pending

(Provide description of a use case matching this scenario with all technical particulars, such as the topological configuration of protocol endpoint entities, potential wireframes, listings and assessments of technical issues, and anything else helpful.)

Scenario: (unique-title)

Submitted by: (participant-name)
Status: pending (change to accepted/deferred/rejected and note the date the decision was made)

(Provide description of the scenario with all nontechnical particulars, noting requirements, constraints, and other observations. Avoid diagrams.)

Use Case: (unique-title)

Submitted by: (participant-name)
Status: pending (change to accepted/deferred/rejected and note the date the decision was made)

(Provide description of a use case matching this scenario with all technical particulars, such as the topological configuration of protocol endpoint entities, potential wireframes, listings and assessments of technical issues, and anything else helpful.)

Change History