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 implementations.
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 forvertical 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,
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 additional languages.