e-Business
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:
StandardUniversal Business Language Naming & Design Rules v1.0 (UBL NDR)
Documents the naming and design rules and guidelines for the
construction of XML components for the UBL vocabulary.
Universal Business Language Naming & Design Rules v1.0 (UBL NDR)
Documents the naming and design rules and guidelines for the
construction of XML components for the UBL vocabulary.
StandardUniversal Business Language (UBL) v1.0:
Defines the Universal Business Language, a generic XML interchange format for business documents that can be restricted or extended to meet the requirements of particular industries.
Universal Business Language (UBL) v1.0:
Defines the Universal Business Language, a generic XML interchange format for business documents that can be restricted or extended to meet the requirements of particular industries.
StandardebXML Message Service Specification v2.0 [OASIS 200204]
Defines a communications-protocol neutral method for exchanging electronic business messages. It defines specific enveloping constructs supporting reliable, secure delivery of business information.
ebXML Message Service Specification v2.0 [OASIS 200204]
Defines a communications-protocol neutral method for exchanging electronic business messages. It defines specific enveloping constructs supporting reliable, secure delivery of business information.
Produced by:
OASIS ebXML Messaging Services TCVoting history:
Voting History for OASIS Standard, August 2004
Additional approvals
ISO/TS 15000-2
OASIS Standard:
The OASIS ebXML Message Service Specification v2.0 OASIS Standard
The related XML Schema
Cite as:
StandardService Provisioning Markup Language (SPML) v1.0, [OASIS 200306]
Defines an XML-based framework for exchanging user, resource, and service provisioning information within and between organizations.
Service Provisioning Markup Language (SPML) v1.0, [OASIS 200306]
Defines an XML-based framework for exchanging user, resource, and service provisioning information within and between organizations.
Produced by:
OASIS Provisioning Services TCVoting history:
October 2003
OASIS Standard:
This specification consists of three documents described and available as follows.
- Core specification document; contains both normative and non-normative description
of the 1.0 specification - Bindings document; contains normative description of SOAP/HTTP & file based transport
bindings - XML Schema; contains the definition of message and protocol formats for SPML V1.0
Cite as:
StandardebXML Collaborative Partner Profile Agreement (CPPA) v2 [OASIS 200206]
Defines the Collaboration-Protocol Profile (CPP) and the Collaboration-Protocol Agreement (CPA), a component of the suite of ebXML specifications. A CPP describes the message exchange capabilities of a party to a business transaction.
ebXML Collaborative Partner Profile Agreement (CPPA) v2 [OASIS 200206]
Defines the Collaboration-Protocol Profile (CPP) and the Collaboration-Protocol Agreement (CPA), a component of the suite of ebXML specifications. A CPP describes the message exchange capabilities of a party to a business transaction.
StandardebXML Registry Information Model (RIM) v2.0 [OASIS 200203]
Defines the services and protocols for an ebXML Registry. A separate document, ebXML Registry: Information Model [ebRIM], defines the types of metadata and content that can be stored in an ebXML Registry.
ebXML Registry Information Model (RIM) v2.0 [OASIS 200203]
Defines the services and protocols for an ebXML Registry. A separate document, ebXML Registry: Information Model [ebRIM], defines the types of metadata and content that can be stored in an ebXML Registry.
No results with the selected filters