OASIS Rights Language Requirements SC

1
OASIS Rights Language Requirements SC

2
Objective Function
RLTC Requirements SC
Requirements
Cost
Objective Maximize Net Utility (Requirements per
Cost)
3
Requirements Workflow
Input
Process
Output
Source
Destination
Standards Initiatives
Categorize
Government/ Regulatory Bodies
Raw Requirements
End Users
Rights Language Requirements
Rights Language Subcommittees
Content/ Web Service Firms
Disposition
Service Providers
Technology Providers
4
Requirements Workflow
Input
Process
Output
Source
Destination
Standards Initiatives
Categorize
Government/ Regulatory Bodies
Raw Requirements
End Users
Rights Language Requirements
Rights Language Subcommittees
Content/ Web Service Firms
Disposition
Service Providers
Technology Providers
Raw Requirements These are the voices of the
customer. Data already exists relative to this
from several different entities such as Standard
Bodies. Tool Formal letter from RLTC to Source
Entities requesting requirements input.
5
Requirements Workflow
Input
Process
Output
Source
Destination
Standards Initiatives
Categorize
Government/ Regulatory Bodies
Raw Requirements
End Users
Rights Language Requirements
Rights Language Subcommittees
Content/ Web Service Firms
Disposition
Service Providers
Technology Providers

• Categorize
• From the Raw Requirements, there needs to be a
  categorization of the data to place into context
  . This will also involve an evaluation of the
  pertinent requirements and its utility with
  respect to the RLTC charter. For example, the SC
  will need to evaluate the requirement relative to
  the need of being industry agnostic.
• Sample Categorizations include
• System vs. Rights Language Requirement
• Architectural (Addressed in the Core)
• Commonly Used (Addressed in the Standard
  Extension)
• Industry Specific (Addressed in an Industry
  Specific Extension)
• Tool
• A Requirements Matrix with a field for
  Categorizations

6
Requirements Workflow
Input
Process
Output
Source
Destination
Standards Initiatives
Categorize
Government/ Regulatory Bodies
Raw Requirements
End Users
Rights Language Requirements
Rights Language Subcommittees
Content/ Web Service Firms
Disposition
Service Providers
Technology Providers
Disposition Each Raw Requirements set will be
dispositioned in that a decision will be made by
the RLTC Requirements SC on the efficient
grouping. The results of the Disposition will be
made available to the entity providing the Raw
Requirements set. For example, if there are 2
requirements that are identical but from
different entities, then the SC should combine
these into 1 requirement and communicated to the
respective Source entities. Tool A disposition
field on the Requirements matrix.
7
Requirements Workflow
Input
Process
Output
Source
Destination
Standards Initiatives
Categorize
Government/ Regulatory Bodies
Raw Requirements
End Users
Rights Language Requirements
Rights Language Subcommittees
Content/ Web Service Firms
Disposition
Service Providers
Technology Providers
Rights Language Requirements The Rights Language
Requirements document will provide the RLTC SCs
with the requirements. There is an iteration here
between the Requirements SC and the other SC to
optimize the Net Utility (See slide 2). This
iteration is not illustrated here. This
optimization may actually happen in real time
since there is cross pollination between several
SCs and the Requirements SC. For example, the
Core and Standard Specification SC should come
back with a cost to integrate a specific
requirement. This will help to prioritize. Tool
Rights Language Requirements Document