OASIS Committee/Project Specification
SAML V2.0 Channel Binding Extensions Version 1.0
Enables extension-aware SAML requesters and responders to modify protocol behavior in a generic, layered fashion. This specification defines an extension to the SAML V2.0 protocol specification that supports the use of channel bindings in conjunction with SAML profiles. It also includes a new SAML profile that applies the extension to a set of profiles that fit a particular communication pattern.
SAML V2.0 Channel Binding Extensions Version 1.0
Enables extension-aware SAML requesters and responders to modify protocol behavior in a generic, layered fashion. This specification defines an extension to the SAML V2.0 protocol specification that supports the use of channel bindings in conjunction with SAML profiles. It also includes a new SAML profile that applies the extension to a set of profiles that fit a particular communication pattern.
Produced by:
OASIS Security Services (SAML) TCVoting history:
July 2013
OASIS Standard:
Cite as:
Cite as:
[SAML-CB-Ext-v1.0] SAML V2.0 Channel Binding Extensions Version 1.0. Edited by Scott Cantor. 10 July 2013. OASIS Committee Specification 01. http://docs.oasis-open.org/security/saml/Post2.0/saml-channel-binding-ext/v1.0/cs01/saml-channel-binding-ext-v1.0-cs01.html. Latest version: http://docs.oasis-open.org/security/saml/Post2.0/saml-channel-binding-ext/v1.0/saml-channel-binding-ext-v1.0.html.
WS-Calendar SOAP-based Services Version 1.0
Describes standard messages and interactions for service interactions with a system that hosts calendar-based information using SOAP. Hosted information can be either traditional personal and enterprise calendar information or services that support XML payloads developed in conformance with the WS-Calendar specification.
WS-Calendar SOAP-based Services Version 1.0
Describes standard messages and interactions for service interactions with a system that hosts calendar-based information using SOAP. Hosted information can be either traditional personal and enterprise calendar information or services that support XML payloads developed in conformance with the WS-Calendar specification.
Produced by:
OASIS Web Services Calendar (WS-Calendar) TCVoting history:
February 2013
OASIS Standard:
Cite as:
Cite as:
[WS-Cal-SOAP]
WS-Calendar SOAP-based Services Version 1.0. Edited by Michael Douglass. 28 February 2013. OASIS Committee Specification 01. http://docs.oasis-open.org/ws-calendar/ws-calendar-soap/v1.0/cs01/ws-calendar-soap-v1.0-cs01.html. Latest version: http://docs.oasis-open.org/ws-calendar/ws-calendar-soap/v1.0/ws-calendar-soap-v1.0.html.
Integrated Collaboration Object Model (ICOM) for Interoperable Collaboration Services Version 1.0
Defines a framework for integrating a broad range of domain models for collaboration activities in an integrated and interoperable collaboration environment.
Integrated Collaboration Object Model (ICOM) for Interoperable Collaboration Services Version 1.0
Defines a framework for integrating a broad range of domain models for collaboration activities in an integrated and interoperable collaboration environment.
Produced by:
OASIS Integrated Collaboration Object Model for Interoperable Collaboration Services (ICOM) TCVoting history:
January 2013
OASIS Standard:
Cite as:
Cite as:
[ICOM-ics-v1.0] Integrated Collaboration Object Model (ICOM) for Interoperable Collaboration Services Version 1.0. . Edited by Eric S. Chan and Patrick Durusau. 31 January 2013. OASIS Committee Specification 01. http://docs.oasis-open.org/icom/icom-ics/v1.0/cs01/icom-ics-v1.0-cs01.html. Latest version: http://docs.oasis-open.org/icom/icom-ics/v1.0/icom-ics-v1.0.html.
Reference Architecture Foundation for Service Oriented Architecture Version 1.0
Specifies the OASIS Reference Architecture Foundation for Service Oriented Architecture (SOA-RAF). It follows from the concepts and relationships defined in the OASIS Reference Model for Service Oriented Architecture as well as work conducted in other organizations. While it remains abstract in nature, the current document describes the foundation upon which specific SOA concrete architectures can be built.
The focus of the SOA-RAF is on an approach to integrating business with the information technology needed to support it. These issues are always present but are all the more important when business integration involves crossing ownership boundaries.
The SOA-RAF follows the recommended practice of describing architecture in terms of models, views, and viewpoints, as prescribed in the ANSI/IEEE 1471-2000.
It has three main views: the Participation in a SOA Ecosystem view which focuses on the way that participants are part of a Service Oriented Architecture ecosystem; the Realization of a SOA Ecosystem view which addresses the requirements for constructing a SOA-based system in a SOA ecosystem; and the Ownership in a SOA Ecosystem view which focuses on what is meant to own a SOA-based system.
The SOA-RAF is of value to Enterprise Architects, Business and IT Architects as well as CIOs and other senior executives involved in strategic business and IT planning.
Reference Architecture Foundation for Service Oriented Architecture Version 1.0
Specifies the OASIS Reference Architecture Foundation for Service Oriented Architecture (SOA-RAF). It follows from the concepts and relationships defined in the OASIS Reference Model for Service Oriented Architecture as well as work conducted in other organizations. While it remains abstract in nature, the current document describes the foundation upon which specific SOA concrete architectures can be built.
The focus of the SOA-RAF is on an approach to integrating business with the information technology needed to support it. These issues are always present but are all the more important when business integration involves crossing ownership boundaries.
The SOA-RAF follows the recommended practice of describing architecture in terms of models, views, and viewpoints, as prescribed in the ANSI/IEEE 1471-2000.
It has three main views: the Participation in a SOA Ecosystem view which focuses on the way that participants are part of a Service Oriented Architecture ecosystem; the Realization of a SOA Ecosystem view which addresses the requirements for constructing a SOA-based system in a SOA ecosystem; and the Ownership in a SOA Ecosystem view which focuses on what is meant to own a SOA-based system.
The SOA-RAF is of value to Enterprise Architects, Business and IT Architects as well as CIOs and other senior executives involved in strategic business and IT planning.
Produced by:
OASIS Service Oriented Architecture Reference Model TCVoting history:
December 2012
OASIS Standard:
Cite as:
Cite as:
[SOA-RAF] Reference Architecture Foundation for Service Oriented Architecture Version 1.0. Edited by Peter Brown, Jeff A. Estefan, Ken Laskey, Francis G. McCabe, and Danny Thornton. 04 December 2012. OASIS Committee Specification 01. http://docs.oasis-open.org/soa-rm/soa-ra/v1.0/cs01/soa-ra-v1.0-cs01.html. Latest version: http://docs.oasis-open.org/soa-rm/soa-ra/v1.0/soa-ra.html.
SAML V2.0 Asynchronous Single Logout Profile Extension Version 1.0
Defines an extension to the SAML 2.0 Single Logout Protocol that allows the initiator to indicate that it does not expect to receive a response from the session authority. This improves user interface interoperability in deployments that want the identity provider to control the user experience during logout.
SAML V2.0 Asynchronous Single Logout Profile Extension Version 1.0
Defines an extension to the SAML 2.0 Single Logout Protocol that allows the initiator to indicate that it does not expect to receive a response from the session authority. This improves user interface interoperability in deployments that want the identity provider to control the user experience during logout.
Produced by:
OASIS Security Services (SAML) TCVoting history:
November 2012
OASIS Standard:
Cite as:
Cite as:
[SAML-Async-SLO] SAML V2.0 Asynchronous Single Logout Profile Extension Version 1.0. Edited by Chad La Joie and Scott Cantor. 22 November 2012. OASIS Committee Specification 01. http://docs.oasis-open.org/security/saml/Post2.0/saml-async-slo/v1.0/cs01/saml-async-slo-v1.0-cs01.html. Latest version: http://docs.oasis-open.org/security/saml/Post2.0/saml-async-slo/v1.0/saml-async-slo-v1.0.html.
Field Force Management Integration Interface Specification Version 1.0
Describes the Field Force Management Integration Interface (FFMII), a flexible interface between Enterprise Resource Management System (ERMS) and Field Force Management System (FFMS).
Field Force Management Integration Interface Specification Version 1.0
Describes the Field Force Management Integration Interface (FFMII), a flexible interface between Enterprise Resource Management System (ERMS) and Field Force Management System (FFMS).
Produced by:
OASIS Field Force Management (FFM) TCVoting history:
October 2012
OASIS Standard:
Cite as:
Cite as:
[FFMII-SPEC-v1.0] Field Force Management Integration Interface Specification Version 1.0. Edited by Thinh Nguyenphu. 05 October 2012. OASIS Committee Specification 01. http://docs.oasis-open.org/ffm/FFMII-SPEC/v1.0/cs01/FFMII-SPEC-v1.0-cs01.html. Latest version: http://docs.oasis-open.org/ffm/FFMII-SPEC/v1.0/FFMII-SPEC-v1.0.html.
SAML V2.0 Metadata Extensions for Registration and Publication Information Version 1.0
Defines a set of extensions to SAML metadata that provide information about the creation and intended usage of the metadata document and information about who and how particular entities were registered.
SAML V2.0 Metadata Extensions for Registration and Publication Information Version 1.0
Defines a set of extensions to SAML metadata that provide information about the creation and intended usage of the metadata document and information about who and how particular entities were registered.
Produced by:
Security Services (SAML) TCVoting history:
April 2012
OASIS Standard:
Cite as:
Cite as:
[SAML-Metadata-RPI-v1.0] SAML V2.0 Metadata Extensions for Registration and Publication Information Version 1.0. Edited by Chad La Joie. 03 April 2012. OASIS Committee Specification 01. http://docs.oasis-open.org/security/saml/Post2.0/saml-metadata-rpi/v1.0/cs01/saml-metadata-rpi-v1.0-cs01.html. Latest version: http://docs.oasis-open.org/security/saml/Post2.0/saml-metadata-rpi/v1.0/saml-metadata-rpi-v1.0.html.
SAML V2.0 Kerberos Web Browser SSO Profile Version 1.0
Allows for transport of assertions using the Kerberos subject confirmation method by standard HTTP user agents with no modification of client software and maximum compatibility with existing deployments. The flow is similar to standard Web Browser SSO, but a Kerberos AP-REQ message is presented by the user agent via the HTTP Negotiate authentication scheme and the Kerberos GSS-API mechanism. The presentation of a valid Kerberos AP-REQ message whose client principal name matches the principal name given in the subject confirmation strengthens the assurance of the resulting authentication context and protects against credential theft.
SAML V2.0 Kerberos Web Browser SSO Profile Version 1.0
Allows for transport of assertions using the Kerberos subject confirmation method by standard HTTP user agents with no modification of client software and maximum compatibility with existing deployments. The flow is similar to standard Web Browser SSO, but a Kerberos AP-REQ message is presented by the user agent via the HTTP Negotiate authentication scheme and the Kerberos GSS-API mechanism. The presentation of a valid Kerberos AP-REQ message whose client principal name matches the principal name given in the subject confirmation strengthens the assurance of the resulting authentication context and protects against credential theft.
Produced by:
Security Services (SAML) TCVoting history:
February 2012
OASIS Standard:
Cite as:
Cite as:
[SAML2KrbSSO] SAML V2.0 Kerberos Web Browser SSO Profile Version 1.0. Edited by Josh Howlett, Thomas Hardjono, Nathan Klingenstein, and Tom Scavo. 07 February 2012. OASIS Committee Specification 01. http://docs.oasis-open.org/security/saml/Post2.0/saml-kerberos-browser-sso/v1.0/cs01/saml-kerberos-browser-sso-v1.0-cs01.html. Latest version: http://docs.oasis-open.org/security/saml/Post2.0/saml-kerberos-browser-sso/v1.0/saml-kerberos-browser-sso-v1.0.html.
Energy Market Information Exchange (EMIX) Version 1.0
Defines an information model and XML vocabulary for the interoperable and standard exchange of prices and product definitions in transactive energy markets:
· Price information
· Bid information
· Time for use or availability
· Units and quantity to be traded
· Characteristics of what is traded
Energy Market Information Exchange (EMIX) Version 1.0
Defines an information model and XML vocabulary for the interoperable and standard exchange of prices and product definitions in transactive energy markets:
· Price information
· Bid information
· Time for use or availability
· Units and quantity to be traded
· Characteristics of what is traded
Produced by:
OASIS Energy Market Information Exchange (eMIX) TCVoting history:
January 2012
OASIS Standard:
Cite as:
Cite as:
[EMIX-v1.0] Energy Market Information Exchange (EMIX) Version 1.0. Edited by Toby Considine. 11 January 2012. OASIS Committee Specification 02. http://docs.oasis-open.org/emix/emix/v1.0/cs02/emix-v1.0-cs02.html. Latest version: http://docs.oasis-open.org/emix/emix/v1.0/emix-v1.0.html.
XML Testing and Event-driven Monitoring of Processes (XTemp) Version 1.0
XTemp is an XML mark-up language that is event-centric and intended for the analysis of a sequence of events that represent traces of business processes. It is designed for both log analysis and real-time execution. It leverages XPath and XSLT.
XML Testing and Event-driven Monitoring of Processes (XTemp) Version 1.0
XTemp is an XML mark-up language that is event-centric and intended for the analysis of a sequence of events that represent traces of business processes. It is designed for both log analysis and real-time execution. It leverages XPath and XSLT.
Produced by:
OASIS Testing and Monitoring Internet Exchanges (TaMIE) TCVoting history:
December 2011
OASIS Standard:
Cite as:
Cite as:
[XTemp-V1.0]
XML Testing and Event-driven Monitoring of Processes (XTemp) Version 1.0. Edited by Jacques Durand and Stephen D. Green. 07 December 2011. OASIS Committee Specification 01. http://docs.oasis-open.org/tamie/xtemp/v1.0/cs01/xtemp-v1.0-cs01.html. Latest version: http://docs.oasis-open.org/tamie/xtemp/v1.0/xtemp-v1.0.html
Test Assertions Part 2 – Test Assertion Markup Language Version 1.0
Defines an XML vocabulary for representing test assertions aligned with the Test Assertions Model.
Test Assertions Part 2 – Test Assertion Markup Language Version 1.0
Defines an XML vocabulary for representing test assertions aligned with the Test Assertions Model.
Produced by:
OASIS Test Assertions Guidelines (TAG) TCVoting history:
November 2011
OASIS Standard:
Cite as:
Cite as:
[TAML]
Test Assertions Part 2 - Test Assertion Markup Language Version 1.0. Edited by Stephen D. Green and Jacques Durand. 30 November 2011. OASIS Committee Specification 02. http://docs.oasis-open.org/tag/taml/v1.0/cs02/testassertionmarkuplanguage-1.0-cs02.html. Latest version: http://docs.oasis-open.org/tag/taml/v1.0/testassertionmarkuplanguage-1.0.html
No results with the selected filters