[oslc] Fw: [members] Call for Participation: OASIS OSLC Lifecycle Integration for Change and Configuration Management (OSLC CCM) TC
Steve K Speicher
sspeiche at us.ibm.com
Mon Jan 6 08:23:32 EST 2014
OSLC Community Members,
See enclosed email for details on the formation of the OASIS OSLC Change
and Configuration Management Technical Committee.
Thanks,
Steve Speicher
IBM Rational Software
OSLC - Lifecycle integration inspired by the web ->
http://open-services.net
----- Forwarded by Steve K Speicher/Raleigh/IBM on 01/06/2014 08:21 AM
-----
From: Chet Ensign <chet.ensign at oasis-open.org>
Date: 01/04/2014 01:11 PM
Subject: [members] Call for Participation: OASIS OSLC Lifecycle
Integration for Change and Configuration Management (OSLC CCM) TC
OASIS members & interested parties,
A new OASIS technical committee is being formed. The OASIS OSLC Lifecycle
Integration for Change and Configuration Management (OSLC CCM) Technical
Committee (TC) has been proposed by the members of OASIS listed in the
charter below. The TC name, statement of purpose, scope, list of
deliverables, audience, IPR mode and language specified in the proposal
will constitute the TC's official charter. Submissions of technology for
consideration by the TC, and the beginning of technical discussions, may
occur no sooner than the TC's first meeting.
The eligibility requirements for becoming a participant in the TC at the
first meeting are:
(a) you must be an employee or designee of an OASIS member organization or
an individual member of OASIS, and
(b) you must join the Technical Committee, which members may do by using
the Roster "join group: link on the TC's web page at [a].
To be considered a voting member at the first meeting:
(a) you must join the Technical Committee at least 7 days prior to the
first meeting (on or before 28 January 2014); and
(b) you must attend the first meeting of the TC, at the time and date
fixed below (04 February 2014).
Participants also may join the TC at a later time. OASIS and the TC
welcomes all interested parties.
Non-OASIS members who wish to participate may contact us about joining
OASIS [b]. In addition, the public may access the information resources
maintained for each TC: a mail list archive, document repository and
public comments facility, which will be linked from the TC's public home
page at [c].
Please feel free to forward this announcement to any other appropriate
lists. OASIS is an open standards organization; we encourage your
participation.
----------
[a] https://www.oasis-open.org/apps/org/workgroup/oslc-ccm/
[b] See http://www.oasis-open.org/join/
[c] http://www.oasis-open.org/committees/oslc-ccm/
----------
CALL FOR PARTICIPATION
OASIS OSLC Lifecycle Integration for Change and Configuration Management
(OSLC CCM) Technical Committee Charter
The charter for this TC is as follows.
(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 one
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 also identify suitable third party
automated test suites, such as an open source suite from Eclipse Lyo, that
can be used to execute such tests.
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, 2014 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 at fluidops.com, fluid Operations OASIS
member
2) Derek Piette, dpiette at ptc.com, PTC OASIS Member
3) Matt Klassen, mklassen at ptc.com, PTC OASIS Member
4) Nick Crossley, ncrossley at us.ibm.com, IBM OASIS Member
5) Parham Vasaiely, parham.vasaiely at eads.com, EADS OASIS member
6) Peter Haase, peter.haase at fluidops.com, fluid Operations OASIS member
7) Robert Baillargeon, rbaillargeon at sodius.com, Sodius OASIS member
8) Samuel Padgett, spadgett at us.ibm.com, IBM OASIS Member
(2)(e) Statements of Support
I, Dave Ings, ings at ca.ibm.com, OASIS primary representative of IBM
organization, confirm our support for this charter and endorse our
proposers listed above as named co-proposers.
I, David Helfinstine, dhelfinstine at ptc.com, OASIS primary representative
of PTC organization, confirm our support for this charter and endorse our
proposers listed above as named co-proposers.
I, Irina Schmidt, irina.schmidt at fluidops.com, OASIS primary representative
of fluid Operations organization, confirm our support for this charter and
endorse our proposers listed above as named co-proposers.
I, Nicolas Figay, nicolas.figay at eads.net, OASIS primary representative of
EADS organization, confirm our support for this charter and endorse our
proposers listed above as named co-proposers.
I, Thomas Capelle, tcapelle at sodius.com, OASIS primary representative of
Sodius organization, 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 at us.ibm.com, OASIS member.
(2)(g) Affiliation to Member Section
The OASIS OSLC CCM TC 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 one 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/community_open-services.net/attachments/20140106/ea02f995/attachment-0003.html>
More information about the Community
mailing list