Skip to end of metadata
Go to start of metadata

Overview of "Share an Org Resource" Use Case

Work with Org member offering a resource to obtain access to the offering


Tip: Key Points
UC Priority= 4 or 5: Critical, is in R2
Only boldface steps are required
<#> before a step —> lower priority
(optional) —> run-time option

Related Jira Issues:   Open   •   All

Metadata

Refer to the Product Description and Product Description Release 2 pages for metadata definitions.

Actors Resource Contributor (e.g., a Data Provider), Resource User (a Registered User)
References Federated Facility Services
UC.R1.34 Share an Org Resource
Uses UC.R2.33 Enroll in an Org
UC.R2.32 Conduct Negotiation
Is Used By  
Extends  
Is Extended By  
In Acceptance Scenarios AS.R2.03A Modelers Integrate External Model with OOI
Technical Notes In the simplest case, the Org is the Integrated Observatory Network.
Lead Team COI
Primary Service Federated Facility Services (Virtual Organization) Part 1
Version 1.1.1
UC Priority 3
UC Status Mapped + Ready
UX Exposure ONC

Summary

This information summarizes the Use Case functionality.

A member of an Org contributes a resource to that Org (for example the Integrated Observatory Network). The terms under which the resource is provided are defined. Another member finds and requests access to the resource. Depending on the terms, the Org may be able to negotiate access on behalf of the contributor, or may pass the negotiation on to the contributor. The resource use is successfully negotiated, and the requesting member gets access.

Assumptions

  • Org exists
  • Resource Contributor has rights to a given resource
  • Resource User is a Registered User in the Org
  • The Org's enrollment contract specifies that a Member contributing a resource commits to responding to negotiations from other Members regarding that resource. (Negotiation role can be delegated to the Org, for example by agreeing to Org's default access rights.)
  • Many of the capabilities in the scenario may be implemented via code, rather than via policy.

Initial State

All entities exist with appropriate rights; no transactions have taken place.

Scenario for "Share an Org Resource" Use Case

  1. A Resource Contributor who wishes to offer a resource for the Org's benefit, contributes (makes available) the resource to the Org.
  2. <2> As authorized by the Org, the Resource Contributor may assert contract conditions on the use of the resource.
    1. This process does not mean giving up control of the resource. (Such is possible, but then the ownership of the resource passes to another entity.)
  3. The Org registers the resource (including contributor and contract conditions).
    1. The Org maintains a listing of all contributed resources and their metadata.
  4. The Resource User consults the Org, and finds and selects a contributed resource of interest.
  5. If necessary, the Org introduces the Resource Contributor to the Resource User for the negotiation of use of the resource.
    1. This introduction may simply happen by providing the metadata describing the Resource Contributor, and some help guidance as to how to proceed.
  6. The requesting and owning Members successfully negotiate use of the resource.
    1. The negotiated agreement is registered by all participants.
    2. The agreement may be satisfied out of band in Release 2 (rather than enabled directly via the Integrated Observatory).
  7. <2> The Resource User uses the resource via mediation of the Integrated Observatory.
    1. Resource User requests a capability on the resource.
    2. The resource, or its agent, validates the request.
    3. - The user and resource each authenticate each other.
    4. - The resource user and resource validate against the contract (authorizations, facts about the contract).
    5. The resource provides the capability (successfully or otherwise.

Final State

The resource has been successfully used according to the contract.

Comments

These comments provide additional context (usually quite technical) for editors of the use case.

(click on # to go to R2 use case)
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20
21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40
41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
61     27B

Labels

r2-usecase r2-usecase Delete
usecase usecase Delete
productdescription productdescription Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.