OASIS Committee/Project Specification
The State of ODF Interoperability Version 1.0
Discusses interoperability with respect to the OASIS OpenDocument Format (ODF) and notes specific areas where implementors might focus in order to improve interoperability among ODF-supporting applications.
The State of ODF Interoperability Version 1.0
Discusses interoperability with respect to the OASIS OpenDocument Format (ODF) and notes specific areas where implementors might focus in order to improve interoperability among ODF-supporting applications.
Produced by:
OASIS Open Document Format Interoperability and Conformance (OIC) TCVoting history:
December 2010
OASIS Standard:
Cite as:
Cite as:
[ODF-Interop-v1.0]
The State of ODF Interoperability Version 1.0. Edited by Robert Weir. 10 December 2010. OASIS Committee Specification 01. http://docs.oasis-open.org/oic/StateOfInterop/v1.0/cs01/StateOfInterop-v1.0-cs01.html. Latest version: http://docs.oasis-open.org/oic/StateOfInterop/v1.0/StateOfInterop.html.
SOA-EERP Business Quality of Service Version 1.0
Specifies the XML vocabulary for business quality of service (bQoS), one of three Specifications for end-to-end resource planning (EERP). Business quality of service describes the business-related characteristics or attributes of a service.
SOA-EERP Business Quality of Service Version 1.0
Specifies the XML vocabulary for business quality of service (bQoS), one of three Specifications for end-to-end resource planning (EERP). Business quality of service describes the business-related characteristics or attributes of a service.
Produced by:
OASIS Service-Oriented Architecture End-to-End Resource Planning (SOA-EERP) TCVoting history:
November 2010
OASIS Standard:
Committee Specification 01
Namespace: http://docs.oasis-open.org/ns/soa-eerp/bqos/200903
Cite as:
Cite as:
[SOA-EERP-bQos]
SOA-EERP Business Quality of Service Version 1.0. Edited by Szu Chang. 25 November 2010. OASIS Committee Specification 01. http://docs.oasis-open.org/soa-eerp/bqos/v1.0/SOA-EERP-bQoS-Spec-cs01.html. Latest version: http://docs.oasis-open.org/soa-eerp/bqos/v1.0/SOA-EERP-bQoS-Specification.html.
SOA-EERP Business Rating of Service Version 1.0
Specifies the XML vocabulary for business rating, one of three Specifications for end-to-end resource planning (EERP). Business rating describes the business-related rating and credentials for a service.
SOA-EERP Business Rating of Service Version 1.0
Specifies the XML vocabulary for business rating, one of three Specifications for end-to-end resource planning (EERP). Business rating describes the business-related rating and credentials for a service.
Produced by:
OASIS Service-Oriented Architecture End-to-End Resource Planning (SOA-EERP) TCVoting history:
November 2010
OASIS Standard:
Cite as:
Cite as:
[SOA-EERP-brating]
SOA-EERP Business Rating of Service Version 1.0. Edited by Szu Chang. 25 November 2010. OASIS Committee Specification 01. http://docs.oasis-open.org/soa-eerp/rt/v1.0/SOA-EERP-bRating-Spec-cs01.html. Latest version: http://docs.oasis-open.org/soa-eerp/rt/v1.0/SOA-EERP-Rating-Specification.html.
SOA-EERP Business Service Level Agreement Version 1.0
Specifies the XML vocabulary for business service level agreement (bSLA), one of three Specifications for end-to-end resource planning (EERP). Business service level agreement describes the agreement between two parties, service requester and service provider, on business-related characteristics or attributes of a service.
SOA-EERP Business Service Level Agreement Version 1.0
Specifies the XML vocabulary for business service level agreement (bSLA), one of three Specifications for end-to-end resource planning (EERP). Business service level agreement describes the agreement between two parties, service requester and service provider, on business-related characteristics or attributes of a service.
Produced by:
OASIS Service-Oriented Architecture End-to-End Resource Planning (SOA-EERP) TCVoting history:
November 2010
OASIS Standard:
Cite as:
Cite as:
[SOA-EERP-bSLA-v1.0] SOA-EERP Business Service Level Agreement Version 1.0. Edited by Szu Chang. 25 November 2010. OASIS Committee Specification 01. http://docs.oasis-open.org/soa-eerp/sla/v1.0/SOA-EERP-bSLA-Spec-cs01.html. Latest version: http://docs.oasis-open.org/soa-eerp/sla/v1.0/SOA-EERP-BSLA-Specification.html.
Product Life Cycle Support DEXs Version R5
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) DEXs standard is defined by Data Exchange Specifications (DEXs) 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 DEXs Version R5
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) DEXs standard is defined by Data Exchange Specifications (DEXs) 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:
November 2010
OASIS Standard:
Committee Specification 01
Cite as:
Cite as:
[PLCS-DEXLIB-VR5] Product Life Cycle Support DEXs Version R5. Edited by Tor Arne Irgens. 18 November 2010. OASIS Committee Specification 01. http://docs.oasis-open.org/plcs/dexlib/cs01/oasis_cover.htm. Latest version: http://docs.oasis-open.org/plcs/dexlib/oasis_cover.htm.
OASIS DSS v1.0 Profile for Comprehensive Multi-Signature Verification Reports Version 1.0
Defines a protocol and processing profile of the DSS Verifying Protocol specified in Section 4 of [DSSCore], which allows to return individual signature verification reports for each signature in a verification request and include detailed information of the different steps taken during verification.
OASIS DSS v1.0 Profile for Comprehensive Multi-Signature Verification Reports Version 1.0
Defines a protocol and processing profile of the DSS Verifying Protocol specified in Section 4 of [DSSCore], which allows to return individual signature verification reports for each signature in a verification request and include detailed information of the different steps taken during verification.
Produced by:
OASIS Digital Signature Services eXtended (DSS-X) TCVoting history:
November 2010
OASIS Standard:
Cite as:
Cite as:
[dxxs-profile-vr-v1.0] OASIS DSS v1.0 Profile for Comprehensive Multi-Signature Verification Reports Version 1.0. Edited by Detlef Huhnlein. 12 November 2010. OASIS Committee Specification 01. http://docs.oasis-open.org/dss-x/profiles/verificationreport/oasis-dssx-1.0-profiles-vr-cs01.html. Latest version: http://docs.oasis-open.org/dss-x/profiles/verificationreport/oasis-dssx-1.0-profiles-vr.html.
SAML V2.0 Identity Assurance Profiles Version 1.0
Specifies methods of representing assurance information in two different aspects of SAML. It provides guidelines for the use of SAML’s Authentication Context [SAMLAC] mechanisms to express authentication assurance information within authentication requests and assertions. Separately, it defines an attribute suitable for inclusion in SAML Metadata [SAMLMeta] for enumerating an Identity Provider’s assurance certifications.
SAML V2.0 Identity Assurance Profiles Version 1.0
Specifies methods of representing assurance information in two different aspects of SAML. It provides guidelines for the use of SAML’s Authentication Context [SAMLAC] mechanisms to express authentication assurance information within authentication requests and assertions. Separately, it defines an attribute suitable for inclusion in SAML Metadata [SAMLMeta] for enumerating an Identity Provider’s assurance certifications.
Produced by:
OASIS Security Services (SAML) TCVoting history:
November 2010
OASIS Standard:
Cite as:
Cite as:
[SAML-assur-prof-v1.0] SAML V2.0 Identity Assurance Profiles Version 1.0. Edited by RL "Bob" Morgan, Paul Madsen, and Scott Cantor. 05 November 2010. OASIS Committee Specification 01. http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-assurance-profile-cs-01.html. Latest version: http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-assurance-profile.html.
Service Provider Request Initiation Protocol and Profile Version 1.0
Defines a generic browser-based protocol by which a request can be made to a service provider to initiate a protocol-specific request for authentication, and to ask that particular options be used when making such a request.
Service Provider Request Initiation Protocol and Profile Version 1.0
Defines a generic browser-based protocol by which a request can be made to a service provider to initiate a protocol-specific request for authentication, and to ask that particular options be used when making such a request.
Produced by:
OASIS Security Services (SAML) TCVoting history:
November 2010
OASIS Standard:
Cite as:
Cite as:
[SAML-request-init-v1.0] Service Provider Request Initiation Protocol and Profile Version 1.0. Edited by Scott Cantor. 05 November 2010. OASIS Committee Specification 01. http://docs.oasis-open.org/security/saml/Post2.0/sstc-request-initiation-cs-01.html. Latest version: http://docs.oasis-open.org/security/saml/Post2.0/sstc-request-initiation.html.
OASIS ebCore Party Id Type Technical Specification Version 1.0
A mechanism for the identification of business partners in business documents based on XML (or other structured formats) and message headers using URN-based identifier types is required in many electronic business exchanges. This specification specifies a formal URN-based mechanism for referencing party types from the ISO 6523, ISO 9735 and ISO 20022 identification scheme catalogs using the oasis URN namespace. Sample applications include (but are not limited to): ebXML message headers; ebXML collaboration protocol profiles and agreements; UBL, UN/CEFACT and OAGIS XML business documents; the UN/CEFACT SBDH; and XBRL documents.
OASIS ebCore Party Id Type Technical Specification Version 1.0
A mechanism for the identification of business partners in business documents based on XML (or other structured formats) and message headers using URN-based identifier types is required in many electronic business exchanges. This specification specifies a formal URN-based mechanism for referencing party types from the ISO 6523, ISO 9735 and ISO 20022 identification scheme catalogs using the oasis URN namespace. Sample applications include (but are not limited to): ebXML message headers; ebXML collaboration protocol profiles and agreements; UBL, UN/CEFACT and OAGIS XML business documents; the UN/CEFACT SBDH; and XBRL documents.
Produced by:
OASIS ebXML Core (ebCore) TCVoting history:
September 2010
OASIS Standard:
Cite as:
Cite as:
[PartyIdType-v1.0] OASIS ebCore Party Id Type Technical Specification Version 1.0. Edited by Dale Moberg and Kathryn Breininger. 28 September 2010. OASIS Committee Specification 01. http://docs.oasis-open.org/ebcore/PartyIdType/v1.0/CS01/PartyIdType-1.0.html. Latest version: http://docs.oasis-open.org/ebcore/PartyIdType/v1.0/PartyIdType-1.0.html.
Election Markup Language (EML) Specification Version 6.0
Describes the background and purpose of the Election Markup Language, the electoral processes from which it derives its structure and the security and audit mechanisms it is designed to support. It also provides an explanation of the core schemas used throughout, definitions of the simple and complex datatypes, plus the EML schemas themselves. It also covers the conventions used in the specification and the use of namespaces, as well as the guidance on the constraints, extendibility, and splitting of messages.
Election Markup Language (EML) Specification Version 6.0
Describes the background and purpose of the Election Markup Language, the electoral processes from which it derives its structure and the security and audit mechanisms it is designed to support. It also provides an explanation of the core schemas used throughout, definitions of the simple and complex datatypes, plus the EML schemas themselves. It also covers the conventions used in the specification and the use of namespaces, as well as the guidance on the constraints, extendibility, and splitting of messages.
Produced by:
OASIS Election and Voter Services TCVoting history:
August 2010
OASIS Standard:
Cite as:
Cite as:
[EML-v6.0] Election Markup Language (EML) Specification Version 6.0. Edited by John Borras and David Webber. 19 August 2010. OASIS Committee Specification 01. http://docs.oasis-open.org/election/eml/v6.0/cs01/EML-Specification-v6.0-cs01.html. Latest version: http://docs.oasis-open.org/election/eml/v6.0/EML-Specification-v6.0.html.
Web Services – Human Task (WS-HumanTask) Specification Version 1.1
Introduces the definition of human tasks, including their properties, behavior and a set of operations used to manipulate human tasks. A coordination protocol is introduced in order to control autonomy and life cycle of service-enabled human tasks in an interoperable manner.
Web Services – Human Task (WS-HumanTask) Specification Version 1.1
Introduces the definition of human tasks, including their properties, behavior and a set of operations used to manipulate human tasks. A coordination protocol is introduced in order to control autonomy and life cycle of service-enabled human tasks in an interoperable manner.
Produced by:
OASIS BPEL4People TCVoting history:
August 2010
OASIS Standard:
Cite as:
Cite as:
[ws-humantask-v1.1] Web Services – Human Task
(WS-HumanTask) Specification Version 1.1. Edited by Luc Clément, Dieter König, Vinkesh Mehta, Ralf Mueller, Ravi Rangaswamy, Michael Rowley, and Ivana Trickovic. 17 August 2010. OASIS Committee Specification 01. http://docs.oasis-open.org/bpel4people/ws-humantask-1.1-spec-cs-01.html. Latest version: http://docs.oasis-open.org/bpel4people/ws-humantask-1.1.html.
WS-BPEL Extension for People (BPEL4People) Specification Version 1.1
Introduces a model for business processes based on Web services. A BPEL process orchestrates interactions among different Web services. The language encompasses features needed to describe complex control flows, including error handling and compensation behavior. In practice, however many business process scenarios require human interactions. A process definition should incorporate people as another type of participants, because humans may also take part in business processes and can influence the process execution.
This specification introduces a BPEL extension to address human interactions in BPEL as a first-class citizen. It defines a new type of basic activity which uses human tasks as an implementation, and allows specifying tasks local to a process or use tasks defined outside of the process definition. This extension is based on the WS-HumanTask specification.
WS-BPEL Extension for People (BPEL4People) Specification Version 1.1
Introduces a model for business processes based on Web services. A BPEL process orchestrates interactions among different Web services. The language encompasses features needed to describe complex control flows, including error handling and compensation behavior. In practice, however many business process scenarios require human interactions. A process definition should incorporate people as another type of participants, because humans may also take part in business processes and can influence the process execution.
This specification introduces a BPEL extension to address human interactions in BPEL as a first-class citizen. It defines a new type of basic activity which uses human tasks as an implementation, and allows specifying tasks local to a process or use tasks defined outside of the process definition. This extension is based on the WS-HumanTask specification.
Produced by:
OASIS BPEL4People TCVoting history:
August 2010
OASIS Standard:
Cite as:
Cite as:
[bpel4people-v1.1] WS-BPEL Extension for People (BPEL4People) Specification Version 1.1. Edited by Luc Clément, Dieter König, Vinkesh Mehta, Ralf Mueller, Ravi Rangaswamy, Michael Rowley, and Ivana Trickovic. 17 August 2010. OASIS Committee Specification 01. http://docs.oasis-open.org/bpel4people/bpel4people-1.1-spec-cs-01.html. Latest version: http://docs.oasis-open.org/bpel4people/bpel4people-1.1.html.
No results with the selected filters