New Features of v2.0.1 in the FAQ

["Sally St. Amand" <sallystamand@yahoo.com>]

When Monica sent out the notice to the user community for the public comment on v2.0.1 she listed all that is new and wonderful. I capsulized each item on her list and included it in the FAQ that is in the works. As we can all atest the list is long. So the question is what are the 6 or 7 features we want to emphasize in the new release, version 2.0.1

 

This is the question presented and answered in the draft FAQ:

 

What are the major features and capabilities that have been added or significantly expanded in ebBP v2.0.1?

 

1. The six business transaction patterns specified by the UN/CEFACT Modeling Methodology (UMM Revision 10, Chapters 8 & 9) for business messaging exchanges have been fully defined. Concrete parameters have been defined and operational semantic spelled out. These six patterns are expected to enable the majority of business transactions in eBusiness or other shared collaborations. In addition, an extensible pattern has been specified to enable future business transactions or business transactions that are industry/partner specific, this pattern is the Data Exchange pattern.
2. Enabled the use of hybrid ebXML and Web Services in the business message exchange. Done by creating an Operational Mapping for the business messages and signals used in the business transaction patterns to abstract WSDL operations used in the WSDL message exchange patterns.
3. The association of semantic elements to conditional expressions through the use of variables. Variables allow abstract elements used in conditional statements (or external specifications) to link to business document contents. Each variable represents an abstract information element that can be defined using XPATH, XSLT, and other expression languages that can be executed on a business document instance. This enables an ebBP definition to reference a set of logical Business Documents.
4. Logical business documents can be specified from multiple sources or namespaces. The actual Business Document can be realized by using external specifications to include ebXML CC and UBL.
5. Business partners can assume different roles throughout the collaboration. These roles can be attached to Business Collaboration definition as it is composed to understanding how the role change enables the business message exchange in a business transaction that is binary or has multiple parties. Expanded role binding capabilities; this supports work of RosettaNet.
6. Third parties involved in the business collaboration but who do not have a role in the business transaction can have visibility to the status of the collaboration.
7. Use of semantic sets to support the capability to take a generic business process and specialize it for a specific use.
8. Improved linking constructs and transition capabilities to support the process definition as they are composed.
9. Defined a general exception that can be used when unplanned activities occur.
10. Provided further definition of the Business Service Interface.
11. Graphically illustrated the business process definition using the Business Process Modeling Notation (BPMN); the current version is in OMG’s standards approval process.
12. Updated the current working draft of the CPP/A (version 2.1) to map to version 2.0.1 of the ebBP, which was defined to support CPP/A.
13. Provided transformation of version 1.05 to ebBP v2.0.1
14. Conscious effort to support interoperability by reflecting the work of standards that have community acceptance and relevance to business process definition.

 

What new features in v2.0.1 should be highlighted by being listed in the FAQ, probably no more than 6 or 7? In what order?

Your thoughts on the listing and any wording.

Thank you

 

Sally