e-Business
StandardAS4 Profile of ebMS 3.0 v1.0
The OASIS ebMS 3.0 Standard combined multiple Web Service standards to create a single comprehensive specification for defining the secure and reliable exchange of documents using Web Services. The AS4 profile of the ebMS 3.0 specification was developed in order to bring continuity to the principles and simplicity that made AS2 successful, while adding better compliance to Web Services standards, and features such as message pulling capability and a built-in Receipt mechanism.
AS4 Profile of ebMS 3.0 v1.0
The OASIS ebMS 3.0 Standard combined multiple Web Service standards to create a single comprehensive specification for defining the secure and reliable exchange of documents using Web Services. The AS4 profile of the ebMS 3.0 specification was developed in order to bring continuity to the principles and simplicity that made AS2 successful, while adding better compliance to Web Services standards, and features such as message pulling capability and a built-in Receipt mechanism.
Produced by:
OASIS ebXML Messaging Services TCVoting history:
January 2013
Additional approvals:
OASIS Standard:
Cite as:
Cite as:
[AS4-Profile ]
AS4 Profile of ebMS 3.0 Version 1.0. Edited by Jacques Durand and Pim van der Eijk. 23 January 2013. OASIS Standard. http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/profiles/AS4-profile/v1.0/os/AS4-profile-v1.0-os.html. Latest version: http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/profiles/AS4-profile/v1.0/AS4-profile-v1.0.html.
StandardReference Architecture Foundation for Service Oriented Architecture Version 1.0
Specifies the OASIS Reference Architecture Foundation for Service Oriented Architecture (SOA-RAF). It follows from the concepts and relationships defined in the OASIS Reference Model for Service Oriented Architecture as well as work conducted in other organizations. While it remains abstract in nature, the current document describes the foundation upon which specific SOA concrete architectures can be built.
The focus of the SOA-RAF is on an approach to integrating business with the information technology needed to support it. These issues are always present but are all the more important when business integration involves crossing ownership boundaries.
The SOA-RAF follows the recommended practice of describing architecture in terms of models, views, and viewpoints, as prescribed in the ANSI/IEEE 1471-2000.
It has three main views: the Participation in a SOA Ecosystem view which focuses on the way that participants are part of a Service Oriented Architecture ecosystem; the Realization of a SOA Ecosystem view which addresses the requirements for constructing a SOA-based system in a SOA ecosystem; and the Ownership in a SOA Ecosystem view which focuses on what is meant to own a SOA-based system.
The SOA-RAF is of value to Enterprise Architects, Business and IT Architects as well as CIOs and other senior executives involved in strategic business and IT planning.
Reference Architecture Foundation for Service Oriented Architecture Version 1.0
Specifies the OASIS Reference Architecture Foundation for Service Oriented Architecture (SOA-RAF). It follows from the concepts and relationships defined in the OASIS Reference Model for Service Oriented Architecture as well as work conducted in other organizations. While it remains abstract in nature, the current document describes the foundation upon which specific SOA concrete architectures can be built.
The focus of the SOA-RAF is on an approach to integrating business with the information technology needed to support it. These issues are always present but are all the more important when business integration involves crossing ownership boundaries.
The SOA-RAF follows the recommended practice of describing architecture in terms of models, views, and viewpoints, as prescribed in the ANSI/IEEE 1471-2000.
It has three main views: the Participation in a SOA Ecosystem view which focuses on the way that participants are part of a Service Oriented Architecture ecosystem; the Realization of a SOA Ecosystem view which addresses the requirements for constructing a SOA-based system in a SOA ecosystem; and the Ownership in a SOA Ecosystem view which focuses on what is meant to own a SOA-based system.
The SOA-RAF is of value to Enterprise Architects, Business and IT Architects as well as CIOs and other senior executives involved in strategic business and IT planning.
Produced by:
OASIS Service Oriented Architecture Reference Model TCVoting history:
December 2012
OASIS Standard:
Cite as:
Cite as:
[SOA-RAF] Reference Architecture Foundation for Service Oriented Architecture Version 1.0. Edited by Peter Brown, Jeff A. Estefan, Ken Laskey, Francis G. McCabe, and Danny Thornton. 04 December 2012. OASIS Committee Specification 01. http://docs.oasis-open.org/soa-rm/soa-ra/v1.0/cs01/soa-ra-v1.0-cs01.html. Latest version: http://docs.oasis-open.org/soa-rm/soa-ra/v1.0/soa-ra.html.
StandardebXML RegRep v4.0
A a standard defining the service interfaces, protocols and information model for an integrated registry and repository. The repository stores digital content while the registry stores metadata that describes the content in the repository.
ebXML RegRep v4.0
A a standard defining the service interfaces, protocols and information model for an integrated registry and repository. The repository stores digital content while the registry stores metadata that describes the content in the repository.
Produced by:
OASIS ebXML Registry TCVoting history:
January 2012
Additional approvals:
OASIS Standard:
This OASIS Standard is composed of the following files:
- Part 0: Overview Document
HTML
PDF
ODT - Part 1: Registry Information Model (ebRIM)
HTML
PDF
ODT - Part 2: Services and Protocols (ebRS)
HTML
PDF
ODT - Part 3: XML Schema
- Part 4: WSDL
- Part 5: XML Definitions
- Distribution ZIP file containing the complete package of the prose specification and related files
Cite as:
StandardProduction Planning and Scheduling (PPS) Version 1.0
Deals with problems of decision-making in all manufacturing companies who want to have a sophisticated information system for production planning and scheduling. PPS specification provides XML schema and communication protocols for information exchange among manufacturing application programs in the web-services environment. The Core Elements section focuses on information model of core elements which can be used as ontology in the production planning and scheduling domain. Since the elements have been designed without particular contexts in planning and scheduling, they can be used in any specific type of messages as a building block depending on the context of application programs. The Transaction Messages section focuses on transaction messages that represent domain information sent or received by application programs in accordance with the context of the communication, as well as transaction rules for contexts such as pushing and pulling of the information required. Finally, the Profile Specifications section focuses on profiles of application programs that may exchange the messages. Application profile and implementation profile are defined. Implementation profile shows capability of application programs in terms of services for message exchange, selecting from all exchange items defined in the application profile. The profile can be used for definition of a minimum level of implementation of application programs which are involved in a community of data exchange.
Production Planning and Scheduling (PPS) Version 1.0
Deals with problems of decision-making in all manufacturing companies who want to have a sophisticated information system for production planning and scheduling. PPS specification provides XML schema and communication protocols for information exchange among manufacturing application programs in the web-services environment. The Core Elements section focuses on information model of core elements which can be used as ontology in the production planning and scheduling domain. Since the elements have been designed without particular contexts in planning and scheduling, they can be used in any specific type of messages as a building block depending on the context of application programs. The Transaction Messages section focuses on transaction messages that represent domain information sent or received by application programs in accordance with the context of the communication, as well as transaction rules for contexts such as pushing and pulling of the information required. Finally, the Profile Specifications section focuses on profiles of application programs that may exchange the messages. Application profile and implementation profile are defined. Implementation profile shows capability of application programs in terms of services for message exchange, selecting from all exchange items defined in the application profile. The profile can be used for definition of a minimum level of implementation of application programs which are involved in a community of data exchange.
Produced by:
OASIS Production Planning and Scheduling TCVoting history:
September 2011
OASIS Standard:
Cite as:
Cite as:
[PPS] Production Planning and Scheduling (PPS) Version 1.0. Edited by Yasuyuki Nishioka and Koichi Wada. 29 September 2011. OASIS Committee Specification 01. http://docs.oasis-open.org/pps/pps/v1.0/cs01/pps-v1.0-cs01.html. Latest version: http://docs.oasis-open.org/pps/pps/v1.0/pps-v1.0.html.
StandardOASIS ebXML Messaging Services Version 3.0: Part 2, Advanced Features
Complements the ebMS 3.0 Core Specification by specifying advanced messaging functionality for message service configuration, message bundling, messaging across intermediaries (multi-hop) and transfer of (compressed) messages as series of smaller message fragments.
OASIS ebXML Messaging Services Version 3.0: Part 2, Advanced Features
Complements the ebMS 3.0 Core Specification by specifying advanced messaging functionality for message service configuration, message bundling, messaging across intermediaries (multi-hop) and transfer of (compressed) messages as series of smaller message fragments.
Produced by:
OASIS ebXML Messaging Services TCVoting history:
May 2011
OASIS Standard:
Cite as:
Cite as:
[ebxml-msg-srv-part2-v3.0] OASIS ebXML Messaging Services Version 3.0: Part 2, Advanced Features. Edited by Jacques Durand, Sander Fieten, and Pim van der Eijk. 19 May 2011. OASIS Committee Specification 01. http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/part2/201004/cs01/ebms-v3.0-part2-cs01.html. Latest version: http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/part2/201004/ebms-v3-part2.html.
StandardOASIS 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.
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.
No results with the selected filters