Projects One Pager

 


ebXML Business Process
- At a glance

Introduction
  The ultimate ebXML goal is to accomplish cross-industry XML-based business process integration. Business events are building blocks that must be understood. The vision of ebXML with respect to business processes is that organizations be able to express their business processes according to a specification to insure that they are understandable by other organizations therby enabling integration of business processes.

The Business Process Project Team will focus on these to define current process requirements and issues. They will NOT be building the processes themselves.

Scope

The ebXML metamodel consists of distinct but interrelated sub-metamodels each corresponding to one of the 6 steps of doing electronic business.

  1. Markets and Parties: For describing and discovering the markets, the market players and their product and service offerings
  2. Resources and Contracts: for describing and discovering contractual terms of the mutual exchange of products or services
  3. Business Processes and Rules: For describing and discovering B2B business processes, i.e. the process enterprises follow when they mutually use each others services
  4. Business Information: For describing and discovering the message structures required for conducting B2B business processes
  5. Business Service Interfaces: For describing and discovering electronic interfaces through which enterprises can electronically use each others services as part of a B2B business process

  6. Transport Protocol: For describing the package went on the wire, and associated protocol properties
  Each specification provides a subset of these sub-metamodels in order to support its area of the ebXML architecture.
  Business Process:
1. Markets and Parties
2. Resource and Contracts
3. Business Processes and Rules

  Core Components:
4. Business Information

  Transport and Routing:
5. Business Service Interfaces
6. Transport Protocol
 

Recent issues of scope involve:

  • Alignment with Core Components. Joint party working on:
      i. Defintions (Core Components vs Common Business Object).
  • tpaML (Trading Partner Agreement Markup Language being an aparallel OASIS project. Resolved by IBM decision to slide the tpaML standardization work over from OASIS into ebXML
  • Marketplace discovery Queried by TA Team but clarified as the need for discovery of products and services within a marketplace

Objectives

  The Business Process Project Team are developing a technical specification for an ebXML-based business process integration accomplished by means of a cross-industry gloabal standard.

ebXML required a methodology be selected to specify "vertical" business processes according to a uniform "template" so they can be compared. Therefore the Team will validate the requirements with at least one instance of cross-industry integration.

Deliverables

 

  • Provide an explicitly specified process metamodel
  • Provide a metamodel that is usable
  • Provide a metamodel compatiblity
  • Enable business to create and maintain a glossary of terms related to business process methodology vocabulary
  • Incorporate these deliverables within the ebXML Registry and Repository
 

Documents current status
June 23- Second Draft Business Process Project Team Technical Specification Document Draft Version 2.0 6/23/00



   

Please address questions or comments regarding this site to webmaster@ebxml.org