History   View   Links to this page Revision from: 2014 January 10 | 10:27 am
This is the revision from 2014 January 10 at 10:27 am   View the current live version of the article.

Contents

New Members

We welcome new members! Remember to sign the participation agreement forms, and please fill out your bio and optionally provide a photo - see the page Nick Crossley for a very short example.

Charter

See the Configuration Management Charter page.

Terminology

See the Configuration Management Terminology page, and the Configuration Management Resource Definitions page. This specification references the emerging work of W3C Linked Data Platform.

See also some legacy Baseline properties proposed by the Core workgroup.

Milestones

Date Milestone Status
2013-12-31 Terminology, use cases, and requirements defined In progress
2013-12-31 First draft specification written In progress
2014-03-31 Draft OSLC SCM migration strategy Not started
2014-04-01 Specification in convergence Not started
2014-07-01 Configuration Management 1.0 enters finalization Not started
2014-06-30 At least one implementation of Configuration Management 1.0 available tbd
TBD Configuration Management 1.0 finalized Not started

Issues

See Configuration Management Issues for a list of open issues.

Scenarios

See Configuration Management Scenarios for scenarios.

Meetings

See Configuration Management Meetings for details on meeting logistics, agendas, and minutes.

Specifications

A draft specification is currently under construction, formed from the contents of the material in the pages Configuration Management Terminology, Configuration Management Resource Definitions, and Configuration Operations.

Document Version Status
None yet

Working Documents

Document Status
Configuration Management Terminology Draft
Configuration Management Resource Definitions Draft
Configuration Operations Draft
Snapshots With Resource Rewriting Legacy from Core workgroup
Snapshots Using Resource State Legacy from Core workgroup

The last two documents are legacy proposals from the Core workgroup: one involves resource rewriting to create new resources that are specific to versions or snapshots of individual resources across multiple service providers, and the other creates snapshot states for a set of resources from a single service provider. Neither of these is necessarily the approach to be used by this workgroup, but they are referenced so we can see what ground has already been covered.

RELM 1.0 RDF Specification, as an example of RDF handling versions, variants, and version skew
PROV Model Primer
Provenance WG homepage
PROV-O: The PROV Ontology
HSUV example in Rational Engineering Lifecycle Manager

Mailing List

Configuration Management mailing list