OASIS Committee/Project Specification
SAML V2.0 Holder-of-Key Web Browser SSO Profile Version 1.0
Allows for transport of holder-of-key assertions 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 an X.509 certificate presented by the user agent via a TLS handshake supplies a key to be used in a holder-of-key assertion. Proof of possession of the private key corresponding to the public key in the certificate resulting from the TLS handshake strengthens the assurance of the resulting authentication context and protects against credential theft. Neither the identity provider nor the service provider is required to validate the certificate.
SAML V2.0 Holder-of-Key Web Browser SSO Profile Version 1.0
Allows for transport of holder-of-key assertions 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 an X.509 certificate presented by the user agent via a TLS handshake supplies a key to be used in a holder-of-key assertion. Proof of possession of the private key corresponding to the public key in the certificate resulting from the TLS handshake strengthens the assurance of the resulting authentication context and protects against credential theft. Neither the identity provider nor the service provider is required to validate the certificate.
Produced by:
OASIS Security Services (SAML) TCVoting history:
August 2010
OASIS Standard:
Cite as:
Cite as:
[SAML-holder-of-key-v1.0] SAML V2.0 Holder-of-Key Web Browser SSO Profile Version 1.0. Edited by Nate Klingenstein and Tom Scavo. 10 August 2010. OASIS Committee Specification 02. http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-holder-of-key-browser-sso-cs-02.html. Latest version: http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-holder-of-key-browser-sso.html.
XACML v3.0 Administration and Delegation Profile Version 1.0
Describes a profile for XACML 3.0 to enable it to express administration and delegation policies.
XACML v3.0 Administration and Delegation Profile Version 1.0
Describes a profile for XACML 3.0 to enable it to express administration and delegation policies.
Produced by:
OASIS eXtensible Access Control Markup Language (XACML) TCVoting history:
August 2010
OASIS Standard:
Cite as:
Cite as:
[XACML-3.0-Admin]
XACML v3.0 Administration and Delegation Profile Version 1.0. Edited by Erik Rissanen. 10 August 2010. OASIS Committee Specification 01. http://docs.oasis-open.org/xacml/3.0/xacml-3.0-administration-v1-spec-cs-01-en.html. Latest version: http://docs.oasis-open.org/xacml/3.0/xacml-3.0-administration-v1-spec-en.html.
SAML V1.1 Information Card Token Profile Version 1.0
Describes a set of rules for Identity Providers and Relying Parties to follow when using SAML V1.1 assertions as managed Information Card security tokens, so that interoperability and security is achieved commensurate with other SAML authentication profiles.
SAML V1.1 Information Card Token Profile Version 1.0
Describes a set of rules for Identity Providers and Relying Parties to follow when using SAML V1.1 assertions as managed Information Card security tokens, so that interoperability and security is achieved commensurate with other SAML authentication profiles.
Produced by:
OASIS Identity Metasystem Interoperability (IMI) TCVoting history:
July 2010
OASIS Standard:
Cite as:
Cite as:
[IMI-SAML1.1-PROFILE] SAML V1.1 Information Card Token Profile Version 1.0. Edited by Michael B. Jones and Scott Cantor. 21 July 2010. OASIS Committee Specification 01. http://docs.oasis-open.org/imi/identity/cs/imi-saml1.1-profile-cs-01.html. Latest version: http://docs.oasis-open.org/imi/identity/imi-saml1.1-profile.html.
SAML V2.0 Information Card Token Profile Version 1.0
Describes a set of rules for Identity Providers and Relying Parties to follow when using SAML V2.0 assertions as managed Information Card security tokens, so that interoperability and security is achieved commensurate with other SAML authentication profiles.
SAML V2.0 Information Card Token Profile Version 1.0
Describes a set of rules for Identity Providers and Relying Parties to follow when using SAML V2.0 assertions as managed Information Card security tokens, so that interoperability and security is achieved commensurate with other SAML authentication profiles.
Produced by:
OASIS Identity Metasystem Interoperability (IMI) TCVoting history:
July 2010
OASIS Standard:
Cite as:
Cite as:
[IMI-SAML2.0-PROFILE] SAML V2.0 Information Card Token Profile Version 1.0. Edited by Scott Cantor and Michael B. Jones. 21 July 2010. OASIS Committee Specification 01. http://docs.oasis-open.org/imi/identity/cs/imi-saml2.0-profile-cs-01.html. Latest version: http://docs.oasis-open.org/imi/identity/imi-saml2.0-profile.html.
Telecom SOA Requirements Version 1.0
Collecting requirements related to technical issues and gaps of SOA standards (specified by OASIS and other SDOs) utilized within the context of Telecoms. Such technical issues are documented in SOA-TEL’s TC first deliverable “Telecom Use Cases and Issues, v.1.0”.
For each of the issues within the “Telecom Use Cases and Issues, v.1.0”, specific requirements are provided within this document. Where possible, non prescriptive solution proposals to the identified issues and requirements are also described, in order to possibly assist those Technical Committees (within OASIS and other SDOs) responsible for the development and maintenance of the SOA related standards.
Telecom SOA Requirements Version 1.0
Collecting requirements related to technical issues and gaps of SOA standards (specified by OASIS and other SDOs) utilized within the context of Telecoms. Such technical issues are documented in SOA-TEL’s TC first deliverable “Telecom Use Cases and Issues, v.1.0”.
For each of the issues within the “Telecom Use Cases and Issues, v.1.0”, specific requirements are provided within this document. Where possible, non prescriptive solution proposals to the identified issues and requirements are also described, in order to possibly assist those Technical Committees (within OASIS and other SDOs) responsible for the development and maintenance of the SOA related standards.
Produced by:
OASIS SOA for Telecom (SOA-Tel) TCVoting history:
June 2010
OASIS Standard:
Cite as:
Cite as:
[soa-tel-req]
Telecom SOA Requirements Version 1.0. Edited by Enrico Ronco. 16 June 2010. OASIS Committee Specification 01. http://docs.oasis-open.org/soa-tel/t-soa-req1.0/cs01/t-soa-req-01-cs-01.html. Latest version: http://docs.oasis-open.org/soa-tel/t-soa-req1.0/t-soa-req-01.html.
Visible Signature Profile of the OASIS Digital Signature Services Version 1.0
Enables to embed visible signature characteristics into documents as part of a digital signature operation and also validate these characteristics as part of the verify signature operation.
Visible Signature Profile of the OASIS Digital Signature Services Version 1.0
Enables to embed visible signature characteristics into documents as part of a digital signature operation and also validate these characteristics as part of the verify signature operation.
Produced by:
OASIS Digital Signature Services eXtended (DSS-X) TCVoting history:
May 2010
OASIS Standard:
Cite as:
Cite as:
[dssx-profiles-visualsig-v1.0] Visible Signature Profile of the OASIS Digital Signature Services Version 1.0. Edited by Ezer Farhi. 08 May 2010. OASIS Committee Specification 01. http://docs.oasis-open.org/dss-x/profiles/visualsig/v1.0/cs01/oasis-dssx-1.0-profiles-visualsig-cs1.html. Latest version: http://docs.oasis-open.org/dss-x/profiles/visualsig/v1.0/oasis-dssx-1.0-profiles-visualsig.html.
OASIS ebXML Messaging Services 3.0 Conformance Profiles
A supplement to the ebMS-3 specification [ebMS3]. It defines some conformance profiles that support specific messaging styles or context of use. Future releases of this document are likely to be augmented with additional conformance profiles that reflect the choices or needs of user communities. As a pre-condition to interoperability it is necessary for two implementations to agree on which common conformance profile, or which compatible conformance profiles, they will comply with. This document and its future releases is intended as a medium to publish conformance profiles that users and products will claim compliance with.
OASIS ebXML Messaging Services 3.0 Conformance Profiles
A supplement to the ebMS-3 specification [ebMS3]. It defines some conformance profiles that support specific messaging styles or context of use. Future releases of this document are likely to be augmented with additional conformance profiles that reflect the choices or needs of user communities. As a pre-condition to interoperability it is necessary for two implementations to agree on which common conformance profile, or which compatible conformance profiles, they will comply with. This document and its future releases is intended as a medium to publish conformance profiles that users and products will claim compliance with.
Produced by:
OASIS ebXML Messaging Services TCVoting history:
April 2010
OASIS Standard:
Cite as:
Cite as:
[ebxml-msg-srv-3.0-conf] OASIS ebXML Messaging Services 3.0 Conformance Profiles. Edited by Jacques Durand. 24 April 2010. OASIS Committee Specification 01. http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/profiles/200707/ebms3-confprofiles-cs-01.html. Latest version: http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/profiles/200707/ebms3-confprofiles.html.
Context/value association using genericode 1.0
Describes the file format used in a “context/value association” file (termed in short as “a CVA file”). This file format is an XML vocabulary using address expressions to specify hierarchical document contexts and their associated constraints. A document context specifies one or more locations found in an XML document or other similarly structured hierarchy of information. A constraint is expressed as either an explicit expression evaluation or as a value inclusion in one or more controlled vocabularies of values. This file format specification assumes a controlled vocabulary of values is expressed in an external resource described by the OASIS genericode standard.
Context/value association using genericode 1.0
Describes the file format used in a “context/value association” file (termed in short as “a CVA file”). This file format is an XML vocabulary using address expressions to specify hierarchical document contexts and their associated constraints. A document context specifies one or more locations found in an XML document or other similarly structured hierarchy of information. A constraint is expressed as either an explicit expression evaluation or as a value inclusion in one or more controlled vocabularies of values. This file format specification assumes a controlled vocabulary of values is expressed in an external resource described by the OASIS genericode standard.
Produced by:
OASIS Code List Representation Technical CommitteeVoting history:
April 2010
OASIS Standard:
Cite as:
Cite as:
[context-value-assoc-v1.0] Context/value association using genericode 1.0. Edited by G. Ken Holman. 15 April 2010. OASIS Committee Specification 01. http://docs.oasis-open.org/codelist/cs01-ContextValueAssociation-1.0/doc/context-value-association.html. Latest version: http://docs.oasis-open.org/codelist/ContextValueAssociation/doc/context-value-association.html.
Telecom SOA Use Cases and Issues Version 1.0
Collecting potential technical issues and gaps of SOA standards (specified by OASIS and other SDOs) utilized within the context of Telecoms.
All perceived technical issues on SOA standards contained in this document are structured with a description of the context, a use case, and a rationalization of the possible gap within the standard.
Amongst future deliverables of the SOA-TEL TC there is a Requirements specification, which will aim to extend the current core SOA enabling stack (Web Services and/or REST, etc.) in support of Telecom needs on the basis of the issues identified within the present document.
Telecom SOA Use Cases and Issues Version 1.0
Collecting potential technical issues and gaps of SOA standards (specified by OASIS and other SDOs) utilized within the context of Telecoms.
All perceived technical issues on SOA standards contained in this document are structured with a description of the context, a use case, and a rationalization of the possible gap within the standard.
Amongst future deliverables of the SOA-TEL TC there is a Requirements specification, which will aim to extend the current core SOA enabling stack (Web Services and/or REST, etc.) in support of Telecom needs on the basis of the issues identified within the present document.
Produced by:
OASIS SOA for Telecom (SOA-Tel) TCVoting history:
March 2010
OASIS Standard:
Cite as:
Cite as:
[soa-tel]
Telecom SOA Use Cases and Issues Version 1.0. Edited by Enrico Ronco. 09 March 2010. OASIS Committee Specification 01. http://docs.oasis-open.org/soa-tel/t-soa-uci/v1.0/cs01/t-soa-uc-cs-01.html. Latest version: http://docs.oasis-open.org/soa-tel/t-soa-uci/v1.0/cd02/t-soa-uc-cd-02.html.
SAML V2.0 Holder-of-Key Assertion Profile Version 1.0
Describes the issuing and processing of holder-of-key SAML assertions. Specifically, we show how a SAML issuer binds X.509 data to a element and how a relying party confirms that a element matches given X.509 data. The binding material used by the SAML issuer and the matching data used by the relying party are obtained from an X.509 certificate.
SAML V2.0 Holder-of-Key Assertion Profile Version 1.0
Describes the issuing and processing of holder-of-key SAML assertions. Specifically, we show how a SAML issuer binds X.509 data to a
Produced by:
OASIS Security Services (SAML) TCVoting history:
January 2010
OASIS Standard:
Cite as:
Cite as:
[SAML-holder-of-key-assert-v1.0] SAML V2.0 Holder-of-Key Assertion Profile Version 1.0. Edited by Tom Scavo. 23 January 2010. OASIS Committee Specification 02. http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml2-holder-of-key-cs-02.html. Latest version: http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml2-holder-of-key.html.
UBL 2 Guidelines for Customization, First Edition
Provides practical guidance in creating UBL-conformant and UBL-compatible document schemas.
UBL 2 Guidelines for Customization, First Edition
Provides practical guidance in creating UBL-conformant and UBL-compatible document schemas.
Produced by:
OASIS Universal Business Language TCVoting history:
July 2009
OASIS Standard:
Cite as:
Cite as:
[UBL-customization]
UBL 2 Guidelines for Customization, First Edition. Edited by Michael Grimley, Mavis Cournane, Tim McGrath, G. Ken Holman, and Jon Bosak. 25 December 2009. OASIS Committee Specification 01. http://docs.oasis-open.org/ubl/guidelines/UBL2-Customization1.0cs01.html. Latest version: http://docs.oasis-open.org/ubl/guidelines/UBL-Customization1.0.html.
Reference Model for Open Architecture for XML Authoring and Localization Version 1.0
Provides a comprehensive, efficient, and cost-effective model for building an XML lifecycle production framework based completely on Open Standards from OASIS, LISA OSCAR and W3C.
Reference Model for Open Architecture for XML Authoring and Localization Version 1.0
Provides a comprehensive, efficient, and cost-effective model for building an XML lifecycle production framework based completely on Open Standards from OASIS, LISA OSCAR and W3C.
Produced by:
Open Architecture for XML Authoring and Localization (OAXAL) TCVoting history:
December 2009
OASIS Standard:
Committee Specification 01
Cite as:
Cite as:
[oaxal-v1.0] Reference Model for Open Architecture for XML Authoring and Localization Version 1.0. Edited by Andrzej Zydroń and Derek Saldana. 12 December 2009. OASIS Committee Specification 01. http://docs.oasis-open.org/oaxal/V1.0/cs01/oaxal-v1.0-cs01.html. Latest version: http://docs.oasis-open.org/oaxal/V1.0/oaxal-v1.0.html.
No results with the selected filters