e-Business
StandardVisible 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.
StandardOASIS 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.
StandardUBL 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.
StandardCustomer Information Quality Party Relationships (xPRL) Specification Version 3.0
Defines the extensible Party Relationships Language (xPRL) specifications of OASIS Customer Information Quality Specifications Version 3.0, a standard way of defining party information and relationships between parties that is vendor neutral and open (i.e., independent of tools, systems, languages and platforms) and enabled portability and interoperability of data, then it would be possible to reduce the expensive and complex Integration problems associated with new business initiatives.
Customer Information Quality Party Relationships (xPRL) Specification Version 3.0
Defines the extensible Party Relationships Language (xPRL) specifications of OASIS Customer Information Quality Specifications Version 3.0, a standard way of defining party information and relationships between parties that is vendor neutral and open (i.e., independent of tools, systems, languages and platforms) and enabled portability and interoperability of data, then it would be possible to reduce the expensive and complex Integration problems associated with new business initiatives.
Produced by:
OASIS Customer Information Quality TCVoting history:
November 2009
OASIS Standard:
Cite as:
Cite as:
[ciq-xprl-v1.0] Customer Information Quality Party Relationships (xPRL) Specification Version 3.0. Edited by Ram Kumar. 11 November 2009. OASIS Committee Specification 01. http://docs.oasis-open.org/ciq/v3.0/xPRL/cs01/specs/ciq-xprl-specs-cs01.html. Latest version: http://docs.oasis-open.org/ciq/v3.0/xPRL/specs/ciq-xprl-specs.html.
StandardUBL 2.0 International Data Dictionary, Volume 1: Japanese, Italian, and Spanish
Provides informative translations of the UBL 2.0 data dictionary into Japanese, Italian, and Spanish.
UBL 2.0 International Data Dictionary, Volume 1: Japanese, Italian, and Spanish
Provides informative translations of the UBL 2.0 data dictionary into Japanese, Italian, and Spanish.
Produced by:
OASIS Universal Business Language TCVoting history:
July 2009
OASIS Standard:
Cite as:
Cite as:
[UBL-idd01]
UBL 2.0 International Data Dictionary, Volume 1: Japanese, Italian, and Spanish Edited by Oriol Bausà Peris, Roberto Cisternino, and Yukinori Saito. 7 July 2009. OASIS Committee Specification 01. http://docs.oasis-open.org/ubl/idd/cs-UBL-2.0-idd01/cs-UBL-2.0-idd01.html. Latest version: http://docs.oasis-open.org/ubl/idd/UBL-2.0-idd.html.
StandardOASIS ebXML Messaging Transport Binding for Digital Signature Services Version 1.0
Mappings from DSS messages into standard communication protocols are called DSS bindings. A transport binding specifies how DSS messages are encoded and carried using a transport protocol. The DSS Core standard [DSS Core] specifies two transport bindings. This document specifies an alternative transport binding that uses the OASIS ebXML Messaging Service. This profile supports is compatible with both the version 2.0 [ebMS 2.0] and version 3.0 [ebMS 3.0] ebXML Messaging OASIS standards.
OASIS ebXML Messaging Transport Binding for Digital Signature Services Version 1.0
Mappings from DSS messages into standard communication protocols are called DSS bindings. A transport binding specifies how DSS messages are encoded and carried using a transport protocol. The DSS Core standard [DSS Core] specifies two transport bindings. This document specifies an alternative transport binding that uses the OASIS ebXML Messaging Service. This profile supports is compatible with both the version 2.0 [ebMS 2.0] and version 3.0 [ebMS 3.0] ebXML Messaging OASIS standards.
Produced by:
OASIS Digital Signature Services eXtended (DSS-X) TCVoting history:
October 2008
OASIS Standard:
Cite as:
Cite as:
[dss-profiles-ebxml-v1.0] OASIS ebXML Messaging Transport Binding for Digital Signature Services Version 1.0. Edited by Pim van der Eijk and Ernst Jan van Nigtevecht. 31 October 2008. OASIS Committee Specification 01. http://docs.oasis-open.org/dss-x/profiles/ebxml/v1.0/cs01/oasis-dss-1.0-profiles-ebxml-cs01.html. Latest version: http://docs.oasis-open.org/dss-x/profiles/ebxml/v1.0/oasis-dss-1.0-profiles-ebxml.html.
StandardCustomer Information Quality Specifications Version 3.0
Defines the OASIS Customer Information Quality Specifications Version 3.0, a standard way of defining party information and relationships between parties that is vendor neutral and open (i.e., independent of tools, systems, languages and platforms) and enabled portability and interoperability of data, then it would be possible to reduce the expensive and complex Integration problems associated with new business initiatives.
Customer Information Quality Specifications Version 3.0
Defines the OASIS Customer Information Quality Specifications Version 3.0, a standard way of defining party information and relationships between parties that is vendor neutral and open (i.e., independent of tools, systems, languages and platforms) and enabled portability and interoperability of data, then it would be possible to reduce the expensive and complex Integration problems associated with new business initiatives.
Produced by:
OASIS Customer Information Quality TCVoting history:
October 2008
OASIS Standard:
Name (xNL), Address (xAL), Name and Address (xNAL) and Party (xPIL)
Committee Specification 02
Cite as:
Cite as:
[ciq-v1.0] Customer Information Quality Specifications Version 3.0
Name (xNL), Address (xAL), Name and Address (xNAL) and Party (xPIL). Edited by Ram Kumar. 02 October 2008. OASIS Committee Specification 02. Distribution package: http://www.oasis-open.org/committees/download.php/29877.
StandardebXML Messaging Services v3.0: Part 1, Core Features
Defines a communications-protocol neutral method for exchanging electronic business messages. It defines specific Web Services-based enveloping constructs supporting reliable, secure delivery of business information. Furthermore, the specification defines a flexible enveloping technique, permitting messages to contain payloads of any format type. This versatility ensures legacy electronic business systems employing traditional syntaxes (i.e. UN/EDIFACT, ASC X12, or HL7) can leverage the advantages of the ebXML infrastructure along with users of emerging technologies.
ebXML Messaging Services v3.0: Part 1, Core Features
Defines a communications-protocol neutral method for exchanging electronic business messages. It defines specific Web Services-based enveloping constructs supporting reliable, secure delivery of business information. Furthermore, the specification defines a flexible enveloping technique, permitting messages to contain payloads of any format type. This versatility ensures legacy electronic business systems employing traditional syntaxes (i.e. UN/EDIFACT, ASC X12, or HL7) can leverage the advantages of the ebXML infrastructure along with users of emerging technologies.
Produced by:
OASIS ebXML Messaging Services TCVoting history:
StandardContent Assembly Mechanism (CAM) v1.1
Provides an open XML based system for using business rules to define, validate and compose specific business documents from generalized schema elements and structures.
The core role of the OASIS CAM specifications is to provide a generic standalone content assembly mechanism that extends beyond the basic structural definition features in XML and schema to provide a comprehensive system with which to define dynamic e-business interoperability.
Content Assembly Mechanism (CAM) v1.1
Provides an open XML based system for using business rules to define, validate and compose specific business documents from generalized schema elements and structures.
The core role of the OASIS CAM specifications is to provide a generic standalone content assembly mechanism that extends beyond the basic structural definition features in XML and schema to provide a comprehensive system with which to define dynamic e-business interoperability.
StandardUniversal Business Language (UBL) v2.0
Defines the Universal Business Language, version 2.0.
Universal Business Language (UBL) v2.0
Defines the Universal Business Language, version 2.0.
StandardBusiness Centric Methodology (BCM) v1.0 Specification
Provides a set of layered methods for acquiring interoperable e-business information within communities of interest. The Standard serves as a road map, enabling organizations to identify and exploit business success factors in a technology-neutral manner.
Business Centric Methodology (BCM) v1.0 Specification
Provides a set of layered methods for acquiring interoperable e-business information within communities of interest. The Standard serves as a road map, enabling organizations to identify and exploit business success factors in a technology-neutral manner.
StandardService Provisioning Markup Language (SPML) v2.0
Defines an XML-based framework for exchanging user, resource, and service provisioning information within and between organizations.
Service Provisioning Markup Language (SPML) v2.0
Defines an XML-based framework for exchanging user, resource, and service provisioning information within and between organizations.
Produced by:
OASIS Provisioning Services TCVoting history:
April 2006
OASIS Standard:
This specification can be downloaded here and consists of three documents described and available as follows.
- OASIS Service Provisioning Markup Language (SPML) v2
- OASIS Service Provisioning Markup Language (SPML) v2 - DSML v2 Profile
- OASIS Service Provisioning Markup Language (SPML) v2 - XSD Profile
Cite as:
No results with the selected filters