ebBP 3/7/2005: Comment re: Conversations (wd 10)

["Monica J. Martin" <Monica.Martin@Sun.COM>]

In last week's call, we discussed several comments and concepts for 
resolution. Expect several emails on these resolutions, of which this is 
the first.
We discussed the mapping to the underlying ebMS and CPA. Here is some 
proposed text for review and comment. Changes clearly identified by 
either UPPER CASE TEXT, full paragraphs or sentences. Thanks!

CBTA/MPC conversation
==================
Section 4.4.4
Change from: The correlation between the different operation invocations 
is implemented at run-time. The specification does not provide
any design-time correlation specification but recommends the use of 
run-time correlation and endpoint references based o
emerging addressing mechanisms such as WS-Addressing, WS-MessageDelivery 
or others.

Change to:
The correlation between the different operation invocations is 
implemented at run-time. THIS specification does not provide
any design-time correlation specification but recommends the use of 
run-time correlation and endpoint references based o
emerging addressing mechanisms such as WS-Addressing, WS-MessageDelivery 
or others.

CORRELATION CAN PROVIDE ADDITIONAL FUNCTIONALITY THAT COULD BE DESIRED 
WHERE COMPLEX COMPOSED ACTIVITIES OCCUR AND VISIBILITY OF THE PARTIES 
AND THEIR ACTIVITIES MUST BE MANAGED.

Section 4.6.7.1
Change from: In the v2.0 technical specification, the nesting for status 
visibility and transitions is unbounded while more business requirements 
are gathered.
Change to:
In the v2.0 technical specification, the nesting for status visibility 
and transitions is unbounded while more business
requirements are gathered.  IN THE FUTURE, IT IS ANTICIPATED THAT 
MANAGING COORDINATED, COMPLEX ACTIVITIES AND
VISIILITY WILL BE EXPANDED FOR BUSINESS COLLABORATION OF MORE THAN TWO 
ABSTRACT PARTIES AND FOR COMPLEXBTA.  SUCH COORDINATION MAY EXPAND THE 
RELATIONSHIP OF THE EBBP TO OTHER EMERGING SPECIFICATIONS AND 
TECHNOLOGIES, IN ORDER TO SUPPORT SPECIALIZED STATUS VISIBILITY, 
PARTICULARLY TO FURTHER ENHANCE MONITORING CAPABILITIES.

Section 4.4.1, 4.4.3
Add at the end of each section:

Conversations between parties are supported by messaging and CPA. Each 
individually and collectively map
to the ebBP. The ebBP provides guidance to the CPA and messaging service 
regarding the processes used,
the constraints expected, and the relationship that exists between the 
parties.

Section 4.6.6.5
Add one sentence in this paragraph:
A Document Envelope can optionally have one or more attachments, all 
related to the primary Business Document. The document
and its attachments in essence form one unit of work in the payload in 
the ebXML Message Service message structure.
Variables and condition expressions can only reference the content of 
the primary business document and not the content of
the attachments. Condition expressions and variables are described in 
further detail later in Section 4.6.8.

".....message structure. VARIABLES AND CONDITION EXPRESSIONS SUPPORT 
IDENTIFICATION OF LOGICAL CONVERSATIONS
BETWEEN PARTIES. Variables and condition expressions [DELETE 'CAN ONLY'] 
reference the content of the primary business.....