OSLC CM Architectural Direction V3

In-progress Working document - supporting specification development for the next version of CM after 2.0. This is not an official list of committed items but a live working document to help prioritize and elaborate on the specification efforts.

The purpose of this page is to collect the architectural direction as driven by scenario priorities for the next version of CM specifications (V3). It also contains various 2.0 issues to be addressed in the next version. This follows on to the CmArchitecturalDirectionV2 work done for 2.0 and CmArchitecturalDirection for 1.0.

Items for Consideration for 3.0

Themes

• IT Operations to Development linkage
• Change Request progress tracking
• More (better) UI delegation
• Filling in the Change Request gaps: attachments, projects, severity, priority, standard types?

Item Details

UNDER DEVELOPMENT (See Backlog)

Spec Backlog

Attachments

Common case is to have potentially many and possibly large attachments associated with Change Requests

Supporting material:

• Scenario: IDE Integration
• Scenario: Application analysis
• V2 Technical Priorities

Project

Need for a container for Change Requests, most (if not all) CM providers have a concept of Project. Though their usage and definition differs.

Supporting material:

• Scenario: IDE Integration

Presentation requirements for resources

Some implementations have assumed different models for what HTML should be returned when requested: should it be contained in an IFrame with just dialog for change request viewing and editing? should it be its own page, with application banner and navigation bar?

Named/Pre-defined Queries

Most, if not all, CM systems have the ability for a user to create a named query to be accessed later for execution. We could fairly rapidly provide at least read-only access to these and execution of queries.

May want to expose this as a query picker/creation tool as done in 1.0 with resources.

Delegated Service Discovery

• better handling of configuration data
• better scaling

Alignment of related standards

• VTODO - need to consider aligning with task management tools?
• OpenSocial - need to evolve our delegated UIs to a widget spec when it is available?
• WSDL 2.0 - RESTful service description

Supporting References

• Scenario Backlog
  • ITOpsToDev
  • CmScenarioDelegatedResourceEditors
• V2 Technical Priorities and backlog
• Experimental Specification and feedback
• V2 Architectural Direction and Backlog
• Possible OSLC priorities and themes for 2011