[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: ebBP 2/21/2005: Pre-Notification Draft for User Communities
As we have discussed, we will be contacting interested user communities
regarding the review of the pre-Committee Draft v2.0 ebBP package. As
promised here is a draft summary to preface with the provided package.
At the end of this email is the initial list of user communities
identified to contact. Others can be added, or specific parties
identified. I encourage your feedback on this draft summary. Thank you.
Summary DRAFT
============
The ebXML Business Process Specification Schema technical specification
is seeking to advance to Committee Draft in OASIS in the ebXML Business
Process TC. The ebXML BPSS (known as ebBP) defines a standardized
language by which business systems may be configured to support
execution of business collaborations. Such business collaborations
consist of business transactions, which are implemented through
semantics such as those defined in one of several concretely defined
standard, extensible or trading partner-specific business transaction
patterns. As part of the ebXML set of specifications, ebBP can
accommodate both the design-time and run-time aspects of eBusiness
processes or Business Collaborations between two or more business
partners. The specification includes a business process specification
schema that may be used either at design (to specify the terms of the
Business Collaboration) or run-time (to effectively or optionally
monitor and/or validates the business message exchange occurrences).
The ebBP TC team is seeking input and feedback from interested user
communities and business sectors on a pre-v2.0 Committee Draft. Many
enhancements and improvements have been made in the v2.0 ebBP including:
* Defined concrete parameters for and operational semantics around
the six business transaction patterns specified in the UN/CEFACT
Modeling Methodology R10 (Chapter 8-9). These patterns specify the
business message exchange (requests, responses and business
signals) applicable to a given business transaction definition.
* Specifies an extensible Data Exchange pattern to enable potential,
future business transaction patterns or those that are partner or
sector specific.
* Created an Operation Mapping that facilitates a map bridge for
business messages and signals used in the business transaction
patterns to abstract WSDL operations used in WSDL message exchange
patterns. This facility may be used in conjunction with the ebXML
CPA or other configuration capabilities to enable the use of
hybrid ebXML and web services in business message exchange.
* Throughout the process lifecycle, enables association of semantic
elements to condition expressions via variables (such as late
binding). Variables allow abstract elements used in conditional
statements as well as external specifications (e.g. business
agreements) to link to business document contents. Each variable
represents an abstract information element defined using XPath,
XSLT and other expression languages that may be executed on a
business document instance.
* Allows two or more business partners to assume many roles and
flexibly attach those roles to the composable Business
Collaboration definitions, while understanding how those role
changes and the binding of them enables the business message
exchange for binary and multi-party interactions.
* Describes status visibility of sub-parties involved in other
Business Transaction Activities (BTA) relevant to actual roles
engaging in a defined Business Transaction Activity via the new
ComplexBTA.
* Improved linking constructs and transition capabilities to support
the composed process definitions.
* Defined a general exception that can be used when unplanned
activities occur in the choreography.
* Provided a more detailed articulation of the Business Service
Interface.
* Visualizes the business process definition using BPMI.org’s
Business Process Modeling Notation (BPMN).
* Provides a mapping to the v2.1 ebXML CPA errata document in
support of the new or improved ebBP constructs (such as role
binding, compositional and OperationMapping capabilities).
* Provides a sample transformation to enable existing
implementations to use the ebBP v2.0. Note this example is under
development and will be provided with the Committee Draft.
* Allows specification of logical business documents from multiple
sources or namespaces.
We encourage you to review the pre-Committee Draft, working technical
specification, schema and examples. Our team is available to meet with
your industry group or target audience experts to enable the promotion
of the OASIS ebBP v2.0 to Committee Draft and on the path to OASIS
Standard. Your support, feedback and comments would be greatly appreciated.
Feedback can be sent to the TC co-chairs, Dale Moberg
(dmoberg@cyclonecommerce.com) or Monica J. Martin
(monica.martin@sun.com) or submitted via the public-comment list on the
OASIS web site. [1] Should you prefer to contact a team member, please
ask them to forward your comments the ebBP team. The package has been
uploaded to the ebxml-bp OASIS site and is publicly available at:
http://www.oasis-open.org/committees/documents.php?wg_abbrev=ebxml-bp
(See Calendar Documents).
Respectfully and sincerely,
The OASIS ebXML Business Process TC
[1] http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ebxml-bp
- See "Send a Comment" button.
[end Summary Draft]
=============================================================================================================
User Community Initial Contact List
========================
JEITA ECOM (ebBP contact: Martin/Nagahashi)
Automotive AIAG (ebBP contact: Webber)
High-tech RosettaNet (ebBP contact: Nagahashi/Moberg)
BizDex Australia (ebBP contact: Martin)
ebXML IIC (ebBP contact: Durand/Fujitsu IT)
BT Telco (ebBP contact: Martin/Roberts)
JBPM (ebBP contact: Schlegel)
Medical Banking and Health Care (ebBP contact: Dodds)
Taiwan ITT (ebBP contact: Martin)
eBSC (ebBP contact: Martin)
CEN-ISSS eBIF (ebBP contact: Martin)
ODETTE (ebBP contact: Martin)
NIST (ebBP contact: Martin)
BPMI/BPMN (Fischer/Martin)
W3C WS-Choreography (ebBP contact: Martin)
Iona (ebBP contact: Martin)
Choreology (ebBP contact: Martin)
UBL (ebBP contact: Martin)
OBIX (ebBP contact: Martin)
SWIFT/FIX (ebBP contact: Martin)
EU Health Care industries / eGov (ebBP contact: Martin)
CIDX-PIDX-RAPID (ebBP contact: Martin)
Aerospace (ebBP contact: Martin)
UN/CEFACT (ebBP contact: Martin)
Other team members will solicit comment within their respective
organizations.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]