ebBP 2/22/2005: Section 4.6.7.1 Status Visibility

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

As discussed in today's teleconference call, more details will be 
provided for the use of status visibility for the Complex BTA. In 
addition, an inquiry has been sent to OAGI and some of the participants 
from AIAG IV&I seeking feedback. Kenji, if you and Dale can provide some 
feedback from RosettaNet, that may be quite helpful. Thanks.

Section 4.6.7.1
1. Change from:
This mechanism allows the status to be known and published in a business 
collaboration. For example, a Buyer and Seller may be parties to the 
business collaboration.....

Change to:
This mechanism allows the status to be known and published in a business 
collaboration, with the default being no status visibility. When status 
visibility is desired, a simple scenario is provided: A Buyer and Seller 
may be partiesy to the business collaboration....

2. Change from:
This decoupling is extremely powerful as incremental improvements in 
both service and business layer evolve.

Change to:
This decoupling is extremely powerful as incremental improvements in 
both service and business layer evolve. If a business process designer 
specifies the document flow from another sub-party, it becomes visible. 
This allows incremental progress in order to anticipate and accommodate 
future development needs by enabling status visibility in a nested 
process.  Other capabilities evolving in the messaging layer (such as in 
future versions of ebXML Messaging Service) may also support this 
projected status requirement.  Such capabilities allow more effective 
monitoring of the activities defined. The process designer may choose to 
use the status visibility details as input to make decisions on other 
business logic used in this enclosing BTA. Industry sectors such as 
logistics processes (particularly for international trade) may make use 
of this mechanism to allow migration to global, potentially fully 
visible, multi-party collaboration.