OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

oasis-charter-discuss message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Proposed Charter for OASIS #OSLC Lifecycle Integration for CCM Technical Committee


To OASIS Members:

A draft TC charter has been submitted to establish the OASIS OSLC Lifecycle Integration for Change and Configuration Management (OSLC CCM) Technical Committee. In accordance with the OASIS TC Process Policy section 2.2: (https://www.oasis-open.org/policies-guidelines/tc-process#formation) the proposed charter is hereby submitted for comment. The comment period shall remain open until 23:59 GMT on 19 December 2013.

OASIS maintains a mailing list for the purpose of submitting comments on proposed charters. Any OASIS member may post to this list by sending email to: oasis-charter-discuss@lists.oasis-open.org. All messages will be publicly archived at: http://lists.oasis-open.org/archives/oasis-charter-discuss/. Members who wish to receive emails must join the group by selecting "join group" on the group home page: http://www.oasis-open.org/apps/org/workgroup/oasis-charter-discuss/. Employees of organizational members do not require primary representative approval to subscribe to the oasis-charter-discuss e-mail.

A telephone conference will be held among the Convener, the OASIS TC Administrator, and those proposers who wish to attend within four days of the close of the comment period. The announcement and call-in information will be noted on the OASIS Charter Discuss Group Calendar.

We encourage member comment and ask that you note the name of the proposed TC (oslc-ccm) in the subject line of your email message.

--- charter for OASIS OSLC Lifecycle Integration for CCM Technical Committee

(1)(a) Name of the TC

OASIS OSLC Lifecycle Integration for Change and Configuration Management (OSLC CCM) Technical Committee 

(1)(b) Statement of Purpose

Managing change and configurations within a complex systems and software development lifecycle can become very difficult, especially in heterogeneous environments including homegrown tools, open source projects, and commercial tools from different vendors. Organizations need to design, develop, deliver, and evolve a portfolio of products with variations in features, configurations, and functions to manage change requests from customers more effectively and efficiently and to align development with business objectives. 

In order to support these activities, there is a need for an open technical architecture that is minimalist, loosely coupled, and standardized. This provides common standardized data formats and operations. The OSLC (Open Services for Lifecycle Collaboration) initiative applies World Wide Web and Linked Data principles, such as those defined in the W3C Linked Data Platform (LDP), to create a cohesive set of specifications that can enable products, services, and other distributed network resources to interoperate successfully. Therefore, the goal of the OSLC Lifecycle Integration for Change and Configuration Management TC (referred to subsequently as the OASIS OSLC CCM TC) is to produce specifications that leverage the OASIS OSLC lifecycle integration Core Specification and enable interoperation of essential change, configuration, and asset management processes across the entire application and product lifecycle to improve transparency, traceability, and agility. The purpose of the OASIS OSLC CCM TC is to define a common set of resources, formats, and RESTful services for use in tools supporting change, configuration, and asset management domains supporting scenarios motived from Application Lifecycle Management (ALM), Product Lifecycle Management (PLM), Integrated Service Management (ISM), Cloud Computing, and DevOps.

(1)(c) Scope

The OASIS OSLC CCM TC defines a set of resources, formats, and a RESTful web services interface for:

Change Management - that is, the management of product change requests, activities, tasks and relationships between those and related resources during the application and product lifecycle. The OASIS OSLC CCM TC will accept as one input the OSLC MS Steering Committee approved versions of the OSLC Change Management 3.0 specifications from open-services.net and targeted for development at OASIS as indicated here: 

http://open-services.net/wiki/change-management/Specification-3.0/

Configuration Management - that is, the management of configurations, configuration items, baselines, and change sets for information resources from any domain. The OASIS OSLC CCM TC will accept as one input the OSLC MS Steering Committee approved versions of the OSLC Configuration Management 1.0 specifications from open-services.net and targeted for development at OASIS as indicated here: 

http://open-services.net/workgroups/configuration-management/

Asset Management - which allows enterprises to catalog, govern, manage, search for, and maintain assets. An asset is anything tangible or intangible that provides value through reference or reuse across a wide audience over an extended period of time such as software, documentation, or representations of equipment. The OASIS OSLC CCM TC will accept as input the OSLC MS Steering Committee approved versions of the OSLC Asset Management 2.0 specifications from open-services.net, targeted for development at OASIS as indicated here: 

http://open-services.net/workgroups/asset-management/

Here are the key responsibilities of the OASIS OSLC CCM TC:

1) Expand on LDP and OSLC Core concepts, as needed, to support integrations with Change and Configuration Management tools, including
  a) Common vocabulary describing change configuration and asset management resources
  b) Standard links between change, configuration and asset management resources and other resources in the software and hardware development lifecycle
  c) State transitions of resources
  d) Binary attachments on resources
  e) Aggregation of configurations of resources across multiple providers 
  f) Integrating tools that already have an existing versioning system, possibly including configurations and baselines, without requiring such tools to re-implement those capabilities. In these cases, the resources to be managed by this cross-tool, cross-domain service may include configurations or baselines defined by existing tools; as such, the service provides composite or aggregate configurations and baselines.

2) Add additional technical elements as required to support current and future scenarios from OSLC User Groups, OSLC MS-affiliated TCs, Subcommittees, and the OSLC Member Section Steering Committee

3) Drive common change, configuration, and asset management and other domain needs with the OSLC Core TC

(1)(d) Deliverables

The OASIS OSLC CCM TC is expected to produce within 24 months of the first meeting:

1) Scenarios: these will guide the priorities and specification contents within the TC
  a) Also a prioritized list of scenarios both developed by the OASIS OSLC CCM TC and contributed from OSLC User Groups, OSLC MS-affiliated TCs, Subcommittees, and the OSLC MS Steering Committee.

2) Specifications: develop specifications to support the identified integration scenarios. The specifications will provide terminology and rules for defining resource vocabularies in terms of the property names and value-types and will recommend various resource representations. 
  a) These deliverables may constitute a collection of specifications, one per capability or a single specification covering a collection of capabilities
  b) Additional specifications may be introduced over time to satisfy capabilities needed by supported scenarios

3) Supporting and enabling material, produced in collaboration with other OSLC MS-affiliated TCs as appropriate or on an as-needed basis to support broad adoption including:
  a) Guidance - informative, non-normative material covering topics such as implementation, resource design, and specification development 
  b) Best Practices - publication of various best (and worst) practices to aid in the implementation of specifications and interoperable solutions. 

4) Terminology: a common set of terms intended to be used across OSLC MS-affiliated TCs

5) Vocabulary: in support of specifications, a set of machine and human processable vocabularies, including tools and best practices

6) Test suites: provide description test suites (perhaps manual) to illustrate how implementations of specifications should comply with the specification. OASIS OSLC CCM TC may identify suitable a third party automated test suite, such as an open source suite from Eclipse Lyo.

The OASIS OSLC CCM TC plans to revise and expand its specifications over time, to enable functionality called for by revisions in, and expansions of, the motivational scenarios.  This means that new specifications that cover new capabilities may be introduced as scenarios are refined to support new capabilities.  The TC may produce separate specifications for various CCM focused areas such as for: Change, Configuration, or Asset Management.

Maintenance

Once the TC has completed work on a specific deliverable (whether "complete" means it has become an OASIS Standard, or simply a Committee Specification is left to the TC's discretion), the TC will provide maintenance for that deliverable. The purpose of maintenance is to provide minor revisions to previously adopted deliverables to clarify ambiguities, inconsistencies, and obvious errors. Maintenance is not intended to enhance a deliverable or to extend its functionality. In addition to maintenance, the TC may choose to create new versions of specifications that support additional capabilities as needed by scenarios.

(1)(e) IPR Mode

This TC will operate under the RF (Royalty Free) on Limited Terms IPR mode as defined in the OASIS Intellectual Property Rights (IPR) Policy. 

(1)(f) Anticipated audience of the work

The OASIS OSLC CCM TC will produce specifications that are applicable to two types of interest groups: 

1) Developers of OSLC specifications, including those produced by OSLC MS-affiliated TCs and other standards groups

2) End users of Specifications, including implementers (software vendors, open source projects, and developers of custom business software) 

The work should be of interest to anyone involved with integration of tools. 

(1)(g) Language

The OASIS OSLC CCM TC will conduct its business in English. The TC may elect to form subcommittees that produce localized documentation of the TC's work in additional languages.

(2) Non-normative information

(2)(a) Identification of similar or related work

1) OSLC Steering Committee approved versions of the OSLC Core specification from open-services.net, targeted for OASIS as indicated here:

http://open-services.net/wiki/core/Specification-3.0/

2) OSLC Steering Committee approved versions of the OSLC Change Management specification from open-services.net, targeted for OASIS as indicated here: 

http://open-services.net/wiki/change-management/Specification-3.0/

3) OSLC Steering Committee approved version of the OSLC Configuration Management specifications from open-services.net, targeted for OASIS as indicated here:

http://open-services.net/workgroups/configuration-management/

4) OSLC MS Steering Committee approved versions of the OSLC Asset Management 2.0 specifications from open-services.net, targeted for OASIS as indicated here: 

http://open-services.net/wiki/asset-management/OSLC-Asset-Management-2.0-Specification/

5) Linked Data Platform 1.0 (Draft) as indicated here: http://www.w3.org/TR/ldp/ 

(2)(b) Date, Time and Location of the first meeting

The first meeting will be held through teleconference on 10:00 AM-12:00PM (EST) February 4, 2013 and IBM will sponsor this call. 

(2)(c) Ongoing meeting schedule

The TC intends to meet by teleconference every two weeks. Sponsorship for these meetings will be rotated through the OASIS Organizational Members represented on the TC. 

(2)(d) The names, electronic mail addresses, and membership affiliations of co-proposers

1) Andreas Eberhart, andreas.eberhart@fluidops.com, fluid Operations  
2) Nick Crossley, ncrossley@us.ibm.com, IBM
3) Parham Vasaiely, parham.vasaiely@eads.com, EADS 
4) Peter Haase, peter.haase@fluidops.com, fluid Operations 
5) Robert Baillargeon, rbaillargeon@sodius.com, Sodius 
6) Samuel Padgett, spadgett@us.ibm.com, IBM 

(2)(e) Statements of Support

I, Dave Ings, ings@ca.ibm.com, primary representative of IBM, confirm our support for this charter and endorse our proposers listed above as named co-proposers. 

I, Irina Schmidt, irina.schmidt@fluidops.com, OASIS primary representative of fluid Operations, confirm our support for this charter and endorse our proposers listed above as named co-proposers.

I, Nicolas Figay, nicolas.figay@eads.net, primary representative of EADS, confirm our support for this charter and endorse our proposers listed above as named co-proposers

I, Thomas Capelle, tcapelle@sodius.com, primary representative of Sodius, confirm our support for this charter and endorse our proposers listed above as named co-proposers 

(2)(f) TC Convener

The TC Convener will be Steve Speicher, sspeiche@us.ibm.com

(2)(g) Affiliation to Member Section 

The OASIS OSLC CCM Technical Committee intends to request affiliation with the OASIS OSLC Member Section (MS): http://www.oasis-oslc.org/

(2)(h) List of anticipated contributions

The OASIS OSLC CCM TC will accept as input from the OSLC Steering Committee approved versions of the OSLC Change Management 3.0 specifications from open-services.net, targeted for OASIS as indicated here http://open-services.net/wiki/change-management/Specification-3.0/, Configuration Management 1.0 specifications from open-services.net, targeted for OASIS as indicated here http://open-services.net/workgroups/configuration-management/, and Asset Management 2.0 Specifications from open-services.net, targeted for OASIS as indicated here http://open-services.net/wiki/asset-management/OSLC-Asset-Management-2.0-Specification/

References

[1] Linked Data Platform 1.0 (Draft)
http://www.w3.org/TR/ldp/ 

[2] Open Services for Lifecycle Collaboration (OSLC)
http://open-services.net/ 

[3] Open Services for Lifecycle Collaboration Core Specification Version 2.0 (Final)
http://open-services.net/bin/view/Main/OslcCoreSpecification/ 

[4] Open Services for Lifecycle Collaboration Core Specification Version 3.0 (Draft)
http://open-services.net/wiki/core/Specification-3.0/

[5] Open Services for Lifecycle Collaboration Change Management Specification Version 2.0 (Final)
http://open-services.net/bin/view/Main/CmSpecificationV2/ 

[6] Open Services for Lifecycle Collaboration Change Management Specification Version 3.0 (Draft)
http://open-services.net/wiki/change-management/Specification-3.0/

[7] Open Services for Lifecycle Collaboration Configuration Management Specification Version 1.0 (Scope)
http://open-services.net/workgroups/configuration-management/

[8] Open Services for Lifecycle Collaboration Asset Management Specification Version 2.0 (Final)
http://open-services.net/wiki/asset-management/OSLC-Asset-Management-2.0-Specification/

[9] Eclipse Lyo
http://eclipse.org/lyo/ 

[10] OASIS IPR Policy
https://www.oasis-open.org/policies-guidelines/ipr/ 


--

/chet 
----------------
Chet Ensign
Director of Standards Development and TC Administration 
OASIS: Advancing open standards for the information society
http://www.oasis-open.org

Primary: +1 973-996-2298
Mobile: +1 201-341-1393 

Check your work using the Support Request Submission Checklist at http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html 

TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin

Follow OASIS on:
LinkedIn:    http://linkd.in/OASISopen
Twitter:        http://twitter.com/OASISopen
Facebook:  http://facebook.com/oasis.open


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]