OASIS Committee Categories: SOA
Technical Committees:
- OASIS Semantic Execution Environment TC
- Developing guidelines, justifications, and implementation directions for deploying Semantic Web services in SOA
- OASIS Service Component Architecture / Assembly (SCA-Assembly) TC
- Defining core SCA composition model for simplifying development of applications using SOA
- OASIS Service Component Architecture / Bindings (SCA-Bindings) TC
- Standardizing bindings for SCA services and references to communication protocols, technologies and frameworks
- OASIS Service Component Architecture / BPEL (SCA-BPEL) TC
- Specifying how SCA component implementations for SOA can be written using BPEL
- OASIS Service Component Architecture / C and C++ (SCA-C-C++) TC
- Standardizing C and C++ use within an SCA domain for SOA
- OASIS Service Component Architecture / J (SCA-J) TC
- Standardizing Java (tm) use within an SCA domain for SOA
- OASIS Service Component Architecture / Policy (SCA-Policy) TC
- Defining an SCA policy framework to simplify SOA application development
- OASIS Service-Oriented Architecture End-to-End Resource Planning (SOA-EERP) TC
- Enabling improved eBusiness process and resource planning at design and run time
- OASIS SOA Reference Model TC
Developing a core reference model to guide and foster the creation of specific, service-oriented architectures- OASIS SOA Repository Artifact Model and Protocol (S-RAMP) TC
- Defining a common data model for SOA repositories as well as an interaction protocol to facilitate the use of common tooling and sharing of data.