ebBP 11/21/2005: Section 2.3 (Detailed Specification of ModelComponents)

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

As discussed last week, we were to consider any more minor editorial 
changes to Section 2.3, emphasizing the composability of ebBP.  Here is 
the text I have thus far, and I'd appreciate updates as the team deems 
appropriate. Please be ready to discuss on Tuesday, 22 November 2005. 
Thank you.


1.1           Detailed Specification of Model Components

[start] As with other specifications in the ebXML framework, an ebBP 
process definition may be composed and used with other technologies.  
That flexibility and composability are important aspects not only to the 
adoption of these standards but their effective use and successful 
deployment into heterogeneous environments and across domains.  In the 
context of this technical specification, Business Collaborations may be 
executed using the ebBP process definition and/or composed with other 
technologies. As it relates to the other specifications in the ebXML 
framework, an ebBP process definition supports the loose coupling and 
alignment needed to execute Business Collaborations. This specification 
may also be used when several other software components are composed and 
being specified to execute Business Collaborations, One example is the 
use of web services mapped to business transactions activities.  The 
ebBP technical specification is used to specify the business process 
related configuration parameters for configuring a BSI to execute and 
monitor these collaborations.

This section discusses:

·         How the ebBP technical specification fits in with other ebXML 
specifications and may be used with other emerging technologies (such as 
WSDL)  An ebBP process definition does not preclude composition with 
other process related technologies.

·         How to use the ebBP artifacts at design time, either for 
specifying brand new collaborations and transactions, or for re-using 
existing ones.

·         How to specify core transaction semantics and parameters 
needed for or that may be used by a Collaboration-Protocol Profile (CPP) 
or Collaboration Protocol Agreement (CPA).

·         Run-time transaction and collaboration semantics that the ebBP 
schema specifies and the BSI is expected to manage.

As this technology matures and relevant profiles emerge, more 
compatibility points will be specified or conformance information (where 
appropriate and applicable) defined in the context of heterogeneous 
technology integration. For example, an ebBP profile is under 
development in OASIS ebXML Implementation, Interoperability Conformance 
(IIC) TC, based on their deployment template.[end]