OASIS Committee/Project Specification
Electronic Identity Credential Trust Elevation Framework Version 1.0
Recommends particular methods as satisfying defined degrees of assurance for elevating trust in an electronic identity credential, to assure the submitter’s identity sufficiently to support elevation between each pair of assurance levels to transact business where material amounts of economic value or personally identifiable data are involved. Alternative and optional methods may be included. The description of each recommended method shall include functional definitions of the types of identity and assertion data employed by each method, and may include specification of the data services required in each elevation, substantive data exchange patterns or models, message exchange patterns or models, and such other elements as the TC deems useful.
Electronic Identity Credential Trust Elevation Framework Version 1.0
Recommends particular methods as satisfying defined degrees of assurance for elevating trust in an electronic identity credential, to assure the submitter’s identity sufficiently to support elevation between each pair of assurance levels to transact business where material amounts of economic value or personally identifiable data are involved. Alternative and optional methods may be included. The description of each recommended method shall include functional definitions of the types of identity and assertion data employed by each method, and may include specification of the data services required in each elevation, substantive data exchange patterns or models, message exchange patterns or models, and such other elements as the TC deems useful.
Produced by:
OASIS Electronic Identity Credential Trust Elevation Methods (Trust Elevation) TCVoting history:
May 2014
OASIS Standard:
Cite as:
Cite as:
[trust-el-framework-v1.0]
Electronic Identity Credential Trust Elevation Framework Version 1.0. Edited by Peter Alterman, Shaheen Abdul Jabbar, Abbie Barbir, Mary Ruddy, and Steve Olshansky. 22 May 2014. OASIS Committee Specification 01. http://docs.oasis-open.org/trust-el/trust-el-framework/v1.0/cs01/trust-el-framework-v1.0-cs01.html. Latest version: http://docs.oasis-open.org/trust-el/trust-el-framework/v1.0/trust-el-framework-v1.0.html.
XACML v3.0 Hierarchical Resource Profile Version 1.0
Provides a profile for the use of XACML with resources that are structured as hierarchies. The profile addresses resources represented as nodes in XML documents or represented in some non-XML way. The profile covers identifying nodes in a hierarchy, requesting access to nodes in a hierarchy, and specifying policies that apply to nodes in a hierarchy.
XACML v3.0 Hierarchical Resource Profile Version 1.0
Provides a profile for the use of XACML with resources that are structured as hierarchies. The profile addresses resources represented as nodes in XML documents or represented in some non-XML way. The profile covers identifying nodes in a hierarchy, requesting access to nodes in a hierarchy, and specifying policies that apply to nodes in a hierarchy.
Produced by:
OASIS eXtensible Access Control Markup Language (XACML) TCVoting history:
May 2014
OASIS Standard:
Cite as:
Cite as:
[xacml-3.0-hierarchical-v1.0]
XACML v3.0 Hierarchical Resource Profile Version 1.0. Edited by Erik Rissanen and Rich Levinson. 18 May 2014. OASIS Committee Specification 02. http://docs.oasis-open.org/xacml/3.0/hierarchical/v1.0/cs02/xacml-3.0-hierarchical-v1.0-cs02.html. Latest version: http://docs.oasis-open.org/xacml/3.0/hierarchical/v1.0/xacml-3.0-hierarchical-v1.0.html.
XACML v3.0 Multiple Decision Profile Version 1.0
Provides a profile for requesting more than one access control decision in a single XACML Request Context, or for requesting a single combined decision based on multiple individual decisions.
XACML v3.0 Multiple Decision Profile Version 1.0
Provides a profile for requesting more than one access control decision in a single XACML Request Context, or for requesting a single combined decision based on multiple individual decisions.
Produced by:
OASIS eXtensible Access Control Markup Language (XACML) TCVoting history:
May 2014
OASIS Standard:
Cite as:
Cite as:
[xacml-3.0-multiple-v1.0]
XACML v3.0 Multiple Decision Profile Version 1.0. Edited by Erik Rissanen. 18 May 2014. OASIS Committee Specification 02. http://docs.oasis-open.org/xacml/3.0/multiple/v1.0/cs02/xacml-3.0-multiple-v1.0-cs02.html. Latest version: http://docs.oasis-open.org/xacml/3.0/multiple/v1.0/xacml-3.0-multiple-v1.0.html.
XACML v3.0 XML Digital Signature Profile Version 1.0
This specification profiles use of the W3C XML-Signature Syntax and Processing Standard in providing authentication and integrity protection for XACML schema instances.
XACML v3.0 XML Digital Signature Profile Version 1.0
This specification profiles use of the W3C XML-Signature Syntax and Processing Standard in providing authentication and integrity protection for XACML schema instances.
Produced by:
OASIS eXtensible Access Control Markup Language (XACML) TCVoting history:
May 2014
OASIS Standard:
Cite as:
Cite as:
[xacml-3.0-dsig-v1.0]
XACML v3.0 XML Digital Signature Profile Version 1.0. Edited by Erik Rissanen. 18 May 2014. OASIS Committee Specification 02. http://docs.oasis-open.org/xacml/3.0/dsig/v1.0/cs02/xacml-3.0-dsig-v1.0-cs02.html. Latest version: http://docs.oasis-open.org/xacml/3.0/dsig/v1.0/xacml-3.0-dsig-v1.0.html.
Transformational Government Framework Version 2.0
A practical “how to” standard for the design and implementation of an effective program of technology-enabled change at national, state or local government level. It describes a managed process of ICT-enabled change within the public sector and in its relationships with the private and voluntary sectors, which puts the needs of citizens and businesses at the heart of that process and which achieves significant and transformational impacts on the efficiency and effectiveness of government.
The TGF provides a tried and tested way forward utilizing the best parts of existing e-Government programs and avoiding large new investments. Its formalization as a Pattern Language enables it to be encapsulated in more formal, tractable, and machine-processable forms, thus making it easy to integrate into desk-top tools and management software aiding testing and assurance of compliance and conformance.
This Work Product constitutes the initial core set of patterns that form the TGF Standard. This set may be revised and/or extended from time to time as appropriate. It replaces and supersedes both the TGF Primer Version 1.0 and the TGF Pattern Languages Core Patterns Version 1.0.
Transformational Government Framework Version 2.0
A practical “how to” standard for the design and implementation of an effective program of technology-enabled change at national, state or local government level. It describes a managed process of ICT-enabled change within the public sector and in its relationships with the private and voluntary sectors, which puts the needs of citizens and businesses at the heart of that process and which achieves significant and transformational impacts on the efficiency and effectiveness of government.
The TGF provides a tried and tested way forward utilizing the best parts of existing e-Government programs and avoiding large new investments. Its formalization as a Pattern Language enables it to be encapsulated in more formal, tractable, and machine-processable forms, thus making it easy to integrate into desk-top tools and management software aiding testing and assurance of compliance and conformance.
This Work Product constitutes the initial core set of patterns that form the TGF Standard. This set may be revised and/or extended from time to time as appropriate. It replaces and supersedes both the TGF Primer Version 1.0 and the TGF Pattern Languages Core Patterns Version 1.0.
Produced by:
OASIS Transformational Government Framework TCVoting history:
May 2014
OASIS Standard:
Cite as:
Cite as:
[TGF-v2.0]
Transformational Government Framework Version 2.0. Edited by John Borras, Peter F Brown, and Chris Parker. 01 May 2014. OASIS Committee Specification 01. http://docs.oasis-open.org/tgf/TGF/v2.0/cs01/TGF-v2.0-cs01.html. Latest version: http://docs.oasis-open.org/tgf/TGF/v2.0/TGF-v2.0.html.
SAML Conformance Clause for AS4/ebMS Version 1.0
Provides a specification as to how an ebMS3/AS4 MSH can support SAML in addition to the username/password and X.509 token profiles of WS-Security for authentication.
The usage of the username/password and X.509 token profiles of WS-Security are defined in some detail in ebMS3 and AS4. SAML is included in ebMS3 but is not defined in detail. AS4 does not discuss SAML.
This document will define the use of SAML in ebMS3 and apply that to the scenarios addressed by AS4.
SAML Conformance Clause for AS4/ebMS Version 1.0
Provides a specification as to how an ebMS3/AS4 MSH can support SAML in addition to the username/password and X.509 token profiles of WS-Security for authentication.
The usage of the username/password and X.509 token profiles of WS-Security are defined in some detail in ebMS3 and AS4. SAML is included in ebMS3 but is not defined in detail. AS4 does not discuss SAML.
This document will define the use of SAML in ebMS3 and apply that to the scenarios addressed by AS4.
Produced by:
OASIS ebXML Messaging Services TCVoting history:
January 2014
OASIS Standard:
Cite as:
Cite as:
[ebMS-saml-conformance] SAML Conformance Clause for AS4/ebMS Version 1.0. Edited by Ian Otto. 30 January 2014. OASIS Committee Specification 01. http://docs.oasis-open.org/ebxml-msg/ebms-v3.0-saml-conformance/v1.0/cs01/ebms-v3.0-saml-conformance-v1.0-cs01.html. Latest version: http://docs.oasis-open.org/ebxml-msg/ebms-v3.0-saml-conformance/v1.0/ebms-v3.0-saml-conformance-v1.0.html..
S-RAMP Version 1.0
Vendors offer tools to facilitate various activities across the life cycle of a SOA artifact, such as design, assembly, quality assurance, deployment and runtime operation of SOA based applications and business processes. The lack of a standardized information model and interaction protocol for artifacts and their metadata residing in a SOA repository means that tools must be customized for use with each different vendor’s SOA repository product. This reduces choice, flexibility and adds costs for customers when choosing tools. This specification defines a SOA artifact data model together with bindings that describe the syntax for interacting with a SOA repository.
S-RAMP Version 1.0
Vendors offer tools to facilitate various activities across the life cycle of a SOA artifact, such as design, assembly, quality assurance, deployment and runtime operation of SOA based applications and business processes. The lack of a standardized information model and interaction protocol for artifacts and their metadata residing in a SOA repository means that tools must be customized for use with each different vendor’s SOA repository product. This reduces choice, flexibility and adds costs for customers when choosing tools. This specification defines a SOA artifact data model together with bindings that describe the syntax for interacting with a SOA repository.
Produced by:
OASIS SOA Repository Artifact Model and Protocol (S-RAMP) TCVoting history:
December 2013
OASIS Standard:
Cite as:
Cite as:
[S-RAMP-v1.0-Foundation] S-RAMP Version 1.0. Part 1: Foundation. Edited by Kurt Stam and Eric Wittmann. 23 December 2013. OASIS Committee Specification 01. http://docs.oasis-open.org/s-ramp/s-ramp/v1.0/cs01/part1-foundation/s-ramp-v1.0-cs01-part1-foundation.html. Latest version: http://docs.oasis-open.org/s-ramp/s-ramp/v1.0/s-ramp-v1.0-part1-foundation.html.
[S-RAMP-v1.0-atom-binding] S-RAMP Version 1.0. Part 2: Atom Binding. Edited by Martin Smithson and Vincent Brunssen. 23 December 2013. OASIS Committee Specification 01. http://docs.oasis-open.org/s-ramp/s-ramp/v1.0/cs01/part2-atom-binding/s-ramp-v1.0-cs01-part2-atom-binding.html. Latest version: http://docs.oasis-open.org/s-ramp/s-ramp/v1.0/s-ramp-v1.0-part2-atom-binding.html.
OData Atom Format Version 4.0
The Open Data Protocol (OData) for representing and interacting with structured content is comprised of a set of specifications. The core specification for the protocol is in OData Version 4.0 Part 1: Protocol. This document extends the core specification by defining representations for OData requests and responses using an Atom format.
OData Atom Format Version 4.0
The Open Data Protocol (OData) for representing and interacting with structured content is comprised of a set of specifications. The core specification for the protocol is in OData Version 4.0 Part 1: Protocol. This document extends the core specification by defining representations for OData requests and responses using an Atom format.
Produced by:
OASIS Open Data Protocol (OData) TCVoting history:
November 2013
OASIS Standard:
Cite as:
Cite as:
[OData-Atom-Format-v4.0] OData Atom Format Version 4.0. Edited by Martin Zurmuehl, Michael Pizzo, and Ralf Handl. 17 November 2013. OASIS Committee Specification 02. http://docs.oasis-open.org/odata/odata-atom-format/v4.0/cs02/odata-atom-format-v4.0-cs02.html. Latest version: http://docs.oasis-open.org/odata/odata-atom-format/v4.0/odata-atom-format-v4.0.html.
Product Life Cycle Support Version 1.0
To establish structured data exchange and sharing capabilities for use by industry to support complex engineered assets throughout their total life cycle. The OASIS Product Life Cycle Support (PLCS) standard is defined by Data Exchange Specifications (DEX) that are based upon ISO 10303 (STEP) Application Protocol 239 Product Life Cycle Support.
The scope of the information content of ISO 10303-239 covers:
The identification and composition of a product design from a support viewpoint;
The definition of documents and their applicability to products and support activities;
The identification and composition of individual products;
Configuration management activities, over the complete life cycle;
Activities required to sustain product function;
The resources needed to perform such activities;
The planning and scheduling of such activities;
The capture of feedback on the performance of such activities, including the resources used;
The capture of feedback on the usage and condition of a product;
The definition of the support environment in terms of people, organizations, skills, experience and facilities.
The business goals of the OASIS PLCS DEXs are to satisfy three significant requirements for owners/operators of complex products and systems such as aircraft, ships and power plants, namely:
Reduction in the total cost of ownership;
Increased asset availability;
Effective information management throughout the product lifecycle.
Product Life Cycle Support Version 1.0
To establish structured data exchange and sharing capabilities for use by industry to support complex engineered assets throughout their total life cycle. The OASIS Product Life Cycle Support (PLCS) standard is defined by Data Exchange Specifications (DEX) that are based upon ISO 10303 (STEP) Application Protocol 239 Product Life Cycle Support.
The scope of the information content of ISO 10303-239 covers:
The identification and composition of a product design from a support viewpoint;
The definition of documents and their applicability to products and support activities;
The identification and composition of individual products;
Configuration management activities, over the complete life cycle;
Activities required to sustain product function;
The resources needed to perform such activities;
The planning and scheduling of such activities;
The capture of feedback on the performance of such activities, including the resources used;
The capture of feedback on the usage and condition of a product;
The definition of the support environment in terms of people, organizations, skills, experience and facilities.
The business goals of the OASIS PLCS DEXs are to satisfy three significant requirements for owners/operators of complex products and systems such as aircraft, ships and power plants, namely:
Reduction in the total cost of ownership;
Increased asset availability;
Effective information management throughout the product lifecycle.
Produced by:
OASIS Product Life Cycle Support (PLCS) TCVoting history:
October 2013
OASIS Standard:
Committee Specification 01
PLCS Platform Specific Models:
Cite as:
Cite as:
[PLCS v1.0] Product Life Cycle Support Version 1.0. Edited by Tor Arne Irgens. 15 October 2013. OASIS Committee Specification 01. http://docs.oasis-open.org/plcs/plcslib/v1.0/cs01/plcslib-v1.0-cs01.html. Latest version: http://docs.oasis-open.org/plcs/plcslib/v1.0/plcslib-v1.0.html.
Emergency Data Exchange Language (EDXL) Distribution Element Version 2.0
Describes a standard message distribution format for data sharing among emergency information systems. The DE 2.0 serves two important purposes:
(1) The DE 2.0 allows an organization to wrap separate but related pieces of emergency information, including any of the EDXL message types, into a single “package” for easier and more useful distribution;
(2) The DE 2.0 allows an organization to “address” the package to organizations or individuals with specified roles, located in specified locations or those interested in specified keywords.
This version of the DE expands the ability to use local community-defined terms, uses a profile of the Geographic Markup Language (GML) , follows best practices for naming conventions, provides the capability to link content objects, supports extensions, and is reorganized for increased flexibility and reuse of common types. The DE 2.0 packages and addresses emergency information for effective distribution with improved standardization and ability to be tailored for user needs.
Emergency Data Exchange Language (EDXL) Distribution Element Version 2.0
Describes a standard message distribution format for data sharing among emergency information systems. The DE 2.0 serves two important purposes:
(1) The DE 2.0 allows an organization to wrap separate but related pieces of emergency information, including any of the EDXL message types, into a single “package” for easier and more useful distribution;
(2) The DE 2.0 allows an organization to “address” the package to organizations or individuals with specified roles, located in specified locations or those interested in specified keywords.
This version of the DE expands the ability to use local community-defined terms, uses a profile of the Geographic Markup Language (GML) , follows best practices for naming conventions, provides the capability to link content objects, supports extensions, and is reorganized for increased flexibility and reuse of common types. The DE 2.0 packages and addresses emergency information for effective distribution with improved standardization and ability to be tailored for user needs.
Produced by:
OASIS Emergency Management TCVoting history:
September 2013
OASIS Standard:
Cite as:
Cite as:
[EDXL-DE-v2.0] Emergency Data Exchange Language (EDXL) Distribution Element Version 2.0. Edited by Jeff Waters. 19 September 2013. OASIS Committee Specification 02. http://docs.oasis-open.org/emergency/edxl-de/v2.0/cs02/edxl-de-v2.0-cs02.html. Latest version: http://docs.oasis-open.org/emergency/edxl-de/v2.0/edxl-de-v2.0.html.
Emergency Data Exchange Language (EDXL) Common Alerting Protocol (CAP) v1.2 Australia (AU) Profile Version 1.0
Describes an interpretation of the OASIS CAP v1.2 standard necessary to meet the needs of the Australian Government.
Emergency Data Exchange Language (EDXL) Common Alerting Protocol (CAP) v1.2 Australia (AU) Profile Version 1.0
Describes an interpretation of the OASIS CAP v1.2 standard necessary to meet the needs of the Australian Government.
Produced by:
OASIS Emergency Management TCVoting history:
September 2013
OASIS Standard:
Cite as:
Cite as:
[EDXL-CAP-AU] Emergency Data Exchange Language (EDXL) Common Alerting Protocol (CAP) v1.2 Australia (AU) Profile Version 1.0. Edited by Gret Trott and Elysa Jones. 05 September 2013. OASIS Committee Specification 02. http://docs.oasis-open.org/emergency/edxl-cap1.2-au/v1.0/cs02/edxl-cap1.2-au-v1.0-cs02.html. Latest version: http://docs.oasis-open.org/emergency/edxl-cap1.2-au/v1.0/edxl-cap1.2-au-v1.0.html.
SAML V2.0 Enhanced Client or Proxy Profile Version 2.0
The SAML V2.0 Enhanced Client or Proxy profile is a SSO profile for use with HTTP, and clients with the capability to directly contact a principal’s identity provider(s) without requiring discovery and redirection by the service provider, as in the case of a browser. This specification updates the original profile by adding support for “Holder of Key” subject confirmation [SAML2HOK] and channel bindings [ChanBind].
SAML V2.0 Enhanced Client or Proxy Profile Version 2.0
The SAML V2.0 Enhanced Client or Proxy profile is a SSO profile for use with HTTP, and clients with the capability to directly contact a principal’s identity provider(s) without requiring discovery and redirection by the service provider, as in the case of a browser. This specification updates the original profile by adding support for “Holder of Key” subject confirmation [SAML2HOK] and channel bindings [ChanBind].
Produced by:
OASIS Security Services (SAML) TCVoting history:
August 2013
OASIS Standard:
Cite as:
Cite as:
[SAML-ecp-v2.0] SAML V2.0 Enhanced Client or Proxy Profile Version 2.0. Edited by Scott Cantor. 26 August 2013. OASIS Committee Specification 01. http://docs.oasis-open.org/security/saml/Post2.0/saml-ecp/v2.0/cs01/saml-ecp-v2.0-cs01.html. Latest version: http://docs.oasis-open.org/security/saml/Post2.0/saml-ecp/v2.0/saml-ecp-v2.0.html.
No results with the selected filters