Asset Management

Introduction

The goal of this effort is to define a common set of resources, formats and RESTful services for the use in Asset Management tools and use by ALM tools.

Refer to the definitions page for descriptions on asset management related terms used here.

Approach and Expectations

The specifications will be developed iteratively by first prioritizing scenarios and focusing on a minimal set of key scenarios. Once these scenarios have been satisfied by specification and proof of implementation, more scenarios will be considered.

Throughout the lifecycle of Propose, Decide, Do, and Deliver there are assets used and others which are created. The Distribute bar represents the asset management activities of Publishing, Searching, and Retrieving assets throughout the lifecycle.

This workgroup will initially focus on the use cases and REST service specifications for Publish, Search, and Retrieve Asset Management Build System Use Cases.

Expectations

The workgroup will perform the following high-level tasks, including:

1. Document the business value of having a standard asset repository service for publishing, searching, and retrieval
2. Describe the relationship of the service specifications to industry standards
3. Achieve understanding of scenarios and document them; initially considering Publish, Search, and Retrieve
   • This requires domain knowledge of asset management integration scenarios
4. Document the RESTful service specifications for the scenarios, such as: Publish, Search, and Retrieve
   • This requires REST skills, XML skills, data definition skills
5. Implement the specification, both service providers and consumers

The workgroup will meet on a regular basis and use this Wiki as the mechanism to communicate work in progress.

Specification Versions

OSLC Asset Management Specification 1.0 (Convergence). Comments on the specification should be logged at the AssetMgSpecificationIssueTracking topic.

Specification Documents

Supporting Documents

Milestones

Note: iterative specification validation will be occuring as the drafts evolve before finalization. The goal is to not develop the specification in abstract; but to do it in parallel with implementations. We will identify the integration opportunities to validate the spec in order for it to be finalized.

Complete Scenario: this means we have documented on the wiki and agreed to the scenarios for which the REST API will be specified/implemented
Start Draft Specs: this means we have sufficient context from the scenarios to begin describing the REST API specs; as the specs mature, so implementing the RETS API based on the specs can begin as well
Start Convergence: this means the spec is 'near final' and final polishing activities begin

Status

Meetings and Agendas