Lists Home |
Date Index |
A new OASIS technical committee is being formed. The OASIS Service
Oriented Architecture Reference Model (SOA-RM) TC has been proposed by the
members of OASIS listed below.
The proposal (below) meets the requirements of the OASIS TC Process
. The TC name, statement of purpose, scope, list of deliverables,
audience, 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.
As specified by the OASIS TC Process, the eligibility requirements for
becoming a participant in the TC at the first meeting are that you must (a)
be an employee of an OASIS member organization or an individual member of
OASIS; (b) notify the TC chair of your intent to participate at least 15
days prior to the first meeting; and (c) attend the first meeting of the
TC, at the time and date fixed below. OASIS members may register and add
themeslves to the roster (as a prospective member or observer) using the
OASIS web-based interface, using the "Join this TC" button on the TC's
public page at . Doing so will inform the TC chair, fulfilling
requirement (b) above, and subscribe you to the TC's e-mail list, where
further organizational details will be posted. OASIS members also may join
the TC after the first meeting.
Standards always are made better by broad participation. Non-OASIS
members who wish to participate may contact us about joining  and review
the web-based membership information at . Our rules and structure are
designed to promote inclusiveness, so we look forward to assisting parties
interested in joining the community of implementers, technologists,
academic and end-users working on OASIS standards. Non-members also may
take advantage of the public resources maintained for each TC: a mail list
archive, document repository and public comments facility, all available on
the TC's home page at . Archives of the TC's mail list and public
comment lists, as with all OASIS TCs, will be visible at .
Further information related to the topic of this TC may be found on
the Cover Pages under the title "Service Oriented Architectures" at
Please feel free to forward this announcement to any other applicable
lists. OASIS is an open standards organization and we encourage your
~ James Bryce Clark
~ Director, Standards Development, OASIS
Name of the TC
OASIS Service Oriented Architecture Reference Model Technical Committee
(abbreviated as OASIS SOA-RM TC).
Statement of Purpose
Problem to be solved: "Service Oriented Architecture" (SOA) as a term is
being used in an increasing number of contexts and specific technology
implementations, sometimes with differing - or worse, conflicting -
understandings of implicit terminology and components. The proposal to
establish a Reference Model is intended to encourage the continued growth
of specific and different SOA implementations whilst preserving a common
layer that can be shared and understood between those or future
Purpose: The SOA-RM TC will deliver a Service Oriented Architecture
Reference Model (SOA-RM). Once the SOA-RM has been delivered, the TC may
consider appropriate follow-up, including the creation of sub-committees,
promotional material, liaisons or other promulgation of the TC's work, in
order to promote the use of the SOA Reference Model in specific SOA
implementations, in particular for vertical industries.
Definitions used in this section:
Reference Model - A reference model is an abstract framework for
understanding significant relationships among the entities of some
environment, and for the development of consistent standards or
specifications supporting that environment. A reference model is based on a
small number of unifying concepts and may be used as a basis for education
and explaining standards to a non-specialist.  A reference model is not
directly tied to any standards, technologies or other concrete
implementation details, but it does seek to provide a common semantics that
can be used unambiguously across and between different implementations.
Architecture - Software architecture for a system is the structure or
structures of the system, which consist of elements and their externally
visible properties, and the relationships among them.
 "Documenting Software Architectures", Addison Wesley, Clements et al,
pp xxv, ISBN 0201703726
Scope of the TC's work
The TC will:
-- deliver a Service Oriented Architecture Reference Model (SOA-RM)
and, if it elects, ancillary materials as described under "purpose" above.
-- allow the commission of sub-committees to create specialized SOA
models for vertical industries or technology families.
-- propose usage and implementation guidelines for creating
specializations of the reference model, whether as a formal methodology or
as best practice guidelines.
In no event shall this Technical Committee finalize or approve any
technical specification if it believes that the use, distribution, or
implementation of such specification would necessarily require the
unauthorized infringement of any third party rights known to the Technical
Committee, and such third party has not agreed to provide necessary license
rights on perpetual, royalty-free, non-discriminatory terms.
1. Service Oriented Architecture Reference Model: completion date in
twelve months from formation of this TC.
2. Specializations of the SOA Reference Model, possibly including
reference architectures, for vertical industries, technology families or
other special interest groups: optional.
Anyone involved in the design, documentation or implementation of Service
Oriented Architectures (SOA's) or components thereof, regardless of the
standards body under which the work is sanctioned.
The TC will conduct its business in English. The TC may elect to form
subcommittees that produce localized documentation of the TC's work in
The following is additional information relevant to the launch of the TC.
Since there are no other reference models currently being worked on in
OASIS, there are no similar deliverables at the time of this submission.
However, a wide variety of specifications, both within and outside of
OASIS, may be of relevance as instances of or components of a specific
service-oriented function or architecture. The objective of the Reference
Model is precisely to provide standardized integration points between
these. The work product of over half of the current OASIS TCs (each of
which may offer a service, service description, advertising mechanism,
service data model or service contract), as well as a large number of
standards from other organizations, may serve as relevant data to inform
the reference model. However, the SOA RM will not seek to choose among
specifications nor populate functions. Similarly, some of the existing
standards-based efforts that claim to describe an architecture or stack of
service-oriented specifications (including the OASIS FWSI and ebSOA TCs,
the W3C Web Services Architecture Technical Note, and other work) may serve
as instances or examples that are relevant data for the creation of the
reference model, but are not comparable, because the reference model will
address a higher level of abstraction.
1. SOA Reference Model Q & A , written by conveners of this TC.
2. Elements of an SOA Reference Model, written by conveners of this TC.
The first meeting of the TC will be held on March 22, 2005, at 8:00 am
Pacific (US) time, by conference call sponsored by Adobe Systems, Inc.
On-going meeting plans.
Meeting schedule will be monthly conference calls as well as quarterly
face-to-face meetings, pending approval and adoption by the TC. Adobe
Systems has agreed to serve as a meeting sponsor
Proposers of the TC
Kathryn Breininger, firstname.lastname@example.org, The Boeing Company
Peter Brown, email@example.com, individual member
Ed Chase, firstname.lastname@example.org, Adobe Systems, Inc.
Joseph Chiusano, email@example.com, Booz Allen Hamilton
John Hardin, firstname.lastname@example.org, individual member
C. Matthew Mackenzie, email@example.com, Adobe Systems
Hamid Ben Malek, HMalek@us.fujitsu.com, Fujitsu
Christopher Mather, firstname.lastname@example.org, Booz Allen Hamilton
Tim Mathews, email@example.com, LMI
Katsuhiro Morita, Km040481@moj.go.jp, ECOM
Duane Nickull, firstname.lastname@example.org, Adobe Systems
Michael E. Ruiz, email@example.com, BAE Systems NA, Inc.
Sally St. Amand, firstname.lastname@example.org, individual member
Ron Schuldt, email@example.com, Lockheed Martin, Inc.
Rajal Shah, firstname.lastname@example.org, Cisco Systems, Inc.
Duane Nickull, email@example.com
Proposed TC chair or co-chairs
Duane Nickull, firstname.lastname@example.org