OASIS (15)

OASIS is a nonprofit consortium that drives the development, convergence and adoption of open standards for the global information society.

The purpose of the OASIS WS-SX TC is to define extensions to OASIS Web Services Security to enable trusted SOAP message exchanges involving multiple message exchanges and to define security policies that govern the formats and tokens of such messages. This work will be carried out through continued refinement of the Web Services SecureConversation, SecurityPolicy and Trust specifications submitted to the TC as referenced in this charter.

Link to website

The purpose of the OASIS WS-RX TC is to define a protocol for reliable message exchanges between two Web services, through continued development of the Web Services Reliable Messaging specification submitted to the TC as referenced in this charter and to define a mechanism by which Web services express support for reliable messaging as well as other related useful parameters. This mechanism will be based upon the Web Services Reliable Messaging Policy Assertion ("WS-RM Policy") specification submitted to the TC.

Link to website

The OASIS WS-BRSP TC maintains WS-I (Web Services Interoperability) Basic Profiles (1.2 and 2.0), Basic Security Profile (1.0), Reliable Secure Profile (1.0), and ISO/IEC JTC 1 Profile Specifications (ISO/IEC 29361:2008 standard Information technology - Web Services Interoperability - WS-I Basic Profile Version 1.1, ISO/IEC 29362:2008 standard Information technology - Web Services Interoperability - WS-I Attachments Profile Version 1.0, ISO/IEC 29363:2008 document Information technology - Web Services Interoperability - WS-I Simple SOAP Binding Profile Version 1.0).

Link to website

The OASIS PMRM TC works to provide a standards-based framework that will help business process engineers, IT analysts, architects, and developers implement privacy and security policies in their operations. PMRM picks up where broad privacy policies leave off. Most policies describe fair information practices and principles but offer little insight into actual implementation. PMRM provides a guideline or template for developing operational solutions to privacy issues. It also serves as an analytical tool for assessing the completeness of proposed solutions and as the basis for establishing categories and groupings of privacy management controls.

Link to website

The OASIS CMIS TC works to standardize a Web services interface specification that will enable greater interoperability of Enterprise Content Management (ECM) systems. CMIS uses Web services and Web 2.0 interfaces to enable rich information to be shared across Internet protocols in vendor-neutral formats, among document systems, publishers and repositories, within one enterprise and between companies.

Link to website

The CloudAuthZ TC develops enhanced models for managing authorizations and entitlements in SaaS, PaaS, and IaaS contexts. CloudAuthZ enables contextual attributes and contextual entitlements sets to be delivered to Policy Enforcement Points in real time. With CloudAuthZ, authorization decisions can be informed by data such as where users are, what they are doing, which device they are using, etc.

Link to website

The OASIS CAMP TC advances an interoperable protocol that cloud implementers can use to package and deploy their applications. CAMP defines interfaces for self-service provisioning, monitoring, and control. Based on REST, CAMP is expected to foster an ecosystem of common tools, plugins, libraries and frameworks, which will allow vendors to offer greater value-add.

Common CAMP use cases include:

  • moving on-premise applications to the cloud (private or public)
  • redeploying applications across cloud platforms from multiple vendors

Link to website

The OASIS PMRM TC works to provide a standards-based framework that will help business process engineers, IT analysts, architects, and developers implement privacy and security policies in their operations.

The OASIS PbD-SE TC provides privacy governance and documentation standards for software engineers. It enables software organizations to embed privacy into the design and architecture of IT systems, without diminishing system functionality.

The OASIS PKCS 11 Technical Committee develops enhancements to improve the PKCS #11 standard for ease of use in code libraries, open source applications, wrappers, and enterprise/COTS products: implementation guidelines, usage tutorials, test scenarios and test suites, interoperability testing, coordination of functional testing, development of conformance profiles, and providing reference implementations.

The OASIS IDCloud TC works to address the serious security challenges posed by identity management in cloud computing.

The OASIS OData TC works to simplify the querying and sharing of data across disparate applications and multiple stakeholders for re-use in the enterprise, Cloud, and mobile devices.

The Name "Customer Information Quality" is just the operating name of the Technical Committee. The scope of the TC is much broader than "Customer Information".

The OASIS XSPA TC works to standardize the way healthcare providers, hospitals, pharmacies, and insurance companies exchange privacy policies, consent directives, and authorizations within and between healthcare organizations.

The OASIS AMQP TC advances a vendor-neutral and platform-agnostic protocol that offers organizations an easier, more secure approach to passing real-time data streams and business transactions.