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


Help: OASIS Mailing Lists Help | MarkMail Help

members message

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

Subject: OASIS TC Call For Participation: OASIS DCML AppServ TC

A new OASIS technical committee is being formed. The OASIS DCML 
Applications and Services (DCML-AppServ) TC has been proposed by the 
following members of OASIS: Mark Darbyshire, Tibco; Jack Kudale, 
Computer Associates; Tim Howes and Phillip Liu, Opsware; J. Darrel 
Thomas, Charles Cooper, Jamie Erbes, and Steve Hulme, Electronic Data 
Systems Corp; Hal Lockhart, BEA; Michael Getz, Computer Associates; Dave 
Roberts, Inkra Networks; Kevin Smith, Fujitsu-Siemens; Chris Burnley, 
Blazent; Barak Perlman, Etagon; Moshe Bar, Qlusters; Noam Fraenkel, 
Mercury Interactive; Duke Tantiprasut, Micromuse, and Josh Sirota, BMC.

The proposal for a new TC meets the requirements of the OASIS TC Process 
(see http://oasis-open.org/committees/process.shtml), and is appended to 
this message. The TC name, statement of purpose, scope, list of 
deliverables, audience, and language specified in the proposal will 
constitute the TC's charter. The TC Process allows these items to be 
clarified (revised); such clarifications (revisions), as well as 
submissions of technology for consideration by the TC and the beginning 
of technical discussions may occur no sooner than the TC's first meeting.

As specified by the OASIS TC Process, the requirements for becoming a 
member of the TC at the first meeting are that you must 1) be an 
employee of an OASIS member organization or an Individual member of 
OASIS; 2) notify the TC chair of your intent to participate at least 15 
days prior to the first meeting; and 3) attend the first meeting of the 
TC. For OASIS members, to register for the TC using the OASIS 
collaborative tools, go to the TC's public web page at 
http://www.oasis-open.org/committees/dcml-appserv and click on the 
button for "Join This TC" at the top of the page. You may add yourself 
to the roster of the TC either as a Prospective Member (if you intend to 
become a member of the TC) or an Observer. A notice will automatically 
be sent to the TC chair, which fulfills requirement #2 above.

OASIS members may also join the TC after the first meeting. Note that 
membership in OASIS TCs is by individual, and not by organization.

Non-OASIS members may read the TC's mail list archive, view the TC's web 
page, and send comments to the TC using a web form available on the TC's 
web page; click the "Send A Comment" button. The archives of the TC's 
mail list and public comments are visible at 

Further information about the topic of this TC may be found on the Cover 
Pages under the title "Standards for Automated Resource Management in 
the Computing Environment" at 

(Please feel free to forward this announcement to any other applicable 


Karl F. Best
Vice President, OASIS
office  +1 978.667.5115 x206     mobile +1 978.761.1648
karl.best@oasis-open.org      http://www.oasis-open.org

Name of the TC

OASIS DCML Applications and Services Technical Committee (DCML-AppServ TC)

Statement of Purpose

The Data Center Markup Language (DCML) is an XML-based specification for 
representing the contents of data centers and information used in 
managing those contents. The overall goal of the OASIS DCML TCs is to 
support the development of a holistic set of standards related to the 
automated management of data center infrastructure. This TC is part of 
the OASIS DCML Member Section.

The purpose of the OASIS DCML Applications and Services TC is to extend 
the OASIS DCML Framework Specification by defining extensions to 
represent Applications and Services and the information necessary to 
manage these components. Applications encompass packaged applications as 
well as custom applications that are used within the data center to 
provide IT services. Services are the finished products of the 
amalgamation of environmental components (servers, storage, networking, 
etc.), blueprinting (configuration information), and policy governing 
components (applications and best practices/processes/guidelines) into 
IT or business services. The Applications and Services extensions will 
be designed so as to be able to represent both specific abstract 
application and services architectures and, if further extended, 
specific products or instantiations of a application or service. As 
noted in the OASIS DCML Framework TC charter, the DCML specifications 
are expected to leverage existing, available standardized methods of 
management, endpoint reference, policy, etc. where appropriate and 

The OASIS DCML Applications and Services TC will directly leverage the 
OASIS DCML Framework specification and provide feedback to the OASIS 
DCML Framework TC to integrate the cross-referencing components of the 
datacenter to ensure uniformity and compliance to the overall DCML 
structure and tenets. The TC will directly utilize the OASIS DCML 
Framework structure, rules, accompanying data model and meta-model, 
which every TC uses to produce extension OASIS DCML definitions, to 
support or constrain the described structure of specific classes of 
applications and services.

The goal of the OASIS DCML Applications and Services TC is to create a 
uniform, heterogeneous, and comprehensive highly-extensible data model 
and interchange format that allows applications (packaged and custom 
developed), application components (e.g., web services, etc.), and IT 
Services of all types to be referenced and managed along with the other 
components of existing and future IT environments. Using the interchange 
format, heterogeneous management systems will be able to incorporate the 
standardized and cross-elemental management packages

Scope of the TC

The scope of the OASIS DCML Applications and Services TC is the 
definition and creation of a data format and associated elements, 
structured hierarchy outlining the format, and specification outlining 
the proper usage of the data format, describing particular Applications 
and Services in IT environments. The scope does not include the creation 
or definition of protocols, programmatic interfaces, or implementations 
that use the specification; this work will be developed separately from 
this TC. There will be likely other OASIS DCML TCs which uniformly 
provide implementation and protocol usage for DCML, but they are yet to 
be determined.

The initial scope of the OASIS DCML Applications and Services TC will 
focus on the use cases provided in the OASIS DCML Framework TC. Using 
base format and structure of the OASIS DCML Framework, the OASIS DCML 
Applications and Services TC will integrate the particular aspects of 
the structure and format of Applications and Services as extensions to 
the OASIS DCML Framework. Due to the complementary nature of these 
extensions to the Framework, the OASIS DCML Applications and Services TC 
work is expected to be able to create much of its work in parallel to 
that of the OASIS DCML Framework TC

It is anticipated that the elements addressed by the Applications & 
Services specification will exclude items addressed by the OASIS DCML 
Networks TC. But the TC may elect to address some or all of those 
elements in consultation with the DCML Networks TC if it facilitates 
unification of the model.

List of Deliverables, with Completion Dates

* Apps/Services Hierarchy and Extension Data Model v1.0 – 2Q 2005,
* Apps/Services Specification v1.0 – 3Q, 2005
* Apps/Services Reference and Users Guide v1.0 – 3Q, 2005
* Apps/Services Specification, Reference and Users Guide v1.1 – 4Q, 2005
* Apps/Services Specification, Reference and Users Guide v2.0 – 1H, 2006
* Apps/Services Specification, Reference and Users Guide v2.1 – 2H, 2006


Generally speaking, the OASIS DCML Applications/Services TC work will be 
used by the same groups that will use other OASIS DCML specifications, 
with a particular interest in the standardization of the management of 
Applications and Services throughout the IT enterprise and software 
management landscape, including the following groups:

* Future TCs tackling the out-of-scope work items mentioned above
* End users seeking to achieve standardized data exchange using DCML for 
particular applications/services
* Vendors and end-users seeking to implement DCML as a means of better 
managing applications/services
* The general public with an interest in learning more about DCML, 
particularly those interested in its application to managing 


The TC will conduct its business in English.

Non-charter information for the purpose of launching the TC:

Similar/Related Work

Based on industry consensus, there is no other similar body of work that 
is synonymous with that of the OASIS DCML TCs. DCML is unique in the 
scope of problem solved and the method by which the problem is solved. 
The OASIS DCML Applications and Services TC will actively collaborate 
with and leverage other organizations and groups creating complementary 
work to DCML, both inside and outside of OASIS, where appropriate, as 
described in the OASIS DCML Framework TC charter. These may include the 

* OASIS DCML Framework TC
* DMTF Common Information Model
* OASIS WSDM TC and other OASIS Web Services TCs
* OASIS ebXML-related TCs

Anticipated Contributions of Existing Work

The proposers intend that the OASIS DCML Applications and Services TC 
use as its starting point the pre-existing specification components 
developed by the DCML Framework and Applications/Services Working Groups 
within the pre-merged DCML Organization.

First Meeting

The first meeting of the TC will be a teleconference meeting hosted by 
the OASIS DCML Member Section on 15 November 2004 at 11:00 am Pacific.

On-going Meeting Schedule

The proposers anticipate that the TC will meet face to face at least 
quarterly, with at least monthly teleconference meetings in between. The 
TC will also conduct technical discussions via email.


Mark Darbyshire <markd@tibco.com> of Tibco
Jack Kudale <Jack.Kudale@ca.com> of Computer Associates
Tim Howes <howes@opsware.com> of Opsware, Inc
J. Darrel Thomas <darrel.thomas@eds.com> of Electronic Data Systems Corp
Charles Cooper <charles.cooper@eds.com> of Electronic Data Systems Corp
Jamie Erbes <jamie.erbes@eds.com> of Electronic Data Systems Corp
Steve Hulme <steve.hulme@eds.com> of Electronic Data Systems Corp
Phillip Liu <phillip@opsware.com>  of Opware, Inc.
Hal Lockhart <hlockhar@bea.com> of BEA, Inc.
Michael Getz <Michael.getz@ca.com> of Computer Associates
Dave Roberts <dave@inkra.com> of Inkra Networks
Kevin Smith <Kevin.Smith@fujitsu-siemens.com> of Fujitsu-Siemens
Chris Burnley <burnley@blazent.com> of Blazent, Inc.
Barak Perlman <barak_perlman@etagon.com> of Etagon, Inc.
Moshe Bar <moshe@qlusters.com> of Qlusters
Noam Fraenkel <nfraenkel@mercury.com> of Mercury Interactive
Duke Tantiprasut <dtantipr@micromuse.com> of Micromuse
Josh Sirota <josh_sirota@bmc.com> of BMC

TC Convener

J. Darrel Thomas, EDS, Darrel.Thomas@EDS.Com

TC Co-Chair Nominees

J. Darrel Thomas, EDS, Darrel.Thomas@EDS.Com
Mark Darbyshire, Tibco, Markd@Tibco.Com

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