[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [ebxml-bp] Re: [ebxml-bp-comment] Public Comment
Radha: I continue as specified to address your questions. 2. ebBP: On specific ebBP possible changes, I will address these individually. This email addresses part of the 2. item. Thanks. > mm1: The CPPA articulates the technical mechanisms that configure a > runtime system and encourage interoperability between two parties that > may use different applications or software from different vendors. The > CPP/A defines the way two parties// will interact in performing the > chosen business collaborations. The BSI understands business > collaborations, the associated BTA, the business state, and the > encompassing conditions, constraints, and expectations of the parties > involved. The CPP/A currently supports the notion of business > transactions between collaborating roles. For example, the CPP/A > currently can provide a reference to timing parameters to a business > collaboration but technical mechanisms are yet to be defined to > accommodate (in CPP/A and in the underlying messaging). Another key > example is for web services. The business process defines a fairly > succinct way to map business transaction activities to an abstract name > for a web service operations. The technical mechanisms for the > interface, the namespace, access, etc. are actually defined by the > configurable capabilities in the CPP/A (as they should be). If this > further description assists in answering your question, is it sufficient > to articulate in the appendices to enable understanding by our user > communities? > > > May be. Will also be of benefit, if the specification can include all > types of models that a versatile B2B gateway should support. > > mm2: In looking at this, I've tried to attempt to consolidate where appropriate to address the descriptive changes possible. Proposed changes affect Section 2.4.1 in the technical specification and Appendix A, as this is where the logical scope of the CPP/A and ebBP may be best understood. One minor update (a cross-reference) is proposed for Section 3.4.9.8. [1] Section 2.4.1 Change from: An ebBP definition/ /is, along with protocol specifications, the object of the agreement between two or more parties. The ebBP definition MAY therefore be incorporated with or referenced by ebXML trading partner Collaboration Protocol Profiles (CPP) or Collaboration Protocol Agreement (CPA). Each CPP MAY declare its support for one or more Roles within the ebBP definition. An ebBP definition is also a machine interpretable specification needed for an ebXML Business Service Interface (BSI), which will enforce its definition at run-time. The CPP profiles and CPA agreements contain further technical parameters resulting in a full specification of the run-time software at each trading partner. Messaging and CPA support conversations between parties. Each individually and collectively map to the ebBP. The ebBP schema (and technical specification) provides guidance to the CPA and messaging service regarding the processes used, the constraints expected, and the relationship that exists between the parties. Change to: An ebBP definition/ /is, along with protocol specifications, the object of the agreement between two or more parties. The ebBP definition MAY therefore be incorporated with or referenced by ebXML trading partner Collaboration Protocol Profiles (CPP) or Collaboration Protocol Agreement (CPA). The CPPA articulates the technical mechanisms that configure a runtime system and encourage interoperability between two parties that may use different applications or software from different vendors. Each CPP MAY declare its support for one or more Roles within the ebBP definition. An ebBP definition is also a machine interpretable specification needed for an ebXML Business Service Interface (BSI), which will enforce its definition at run-time. The CPP profiles and CPA agreements contain further technical parameters resulting in a full specification of the run-time software at each trading partner. The CPA currently supports the notion of business transactions between collaborating roles. Messaging and CPA support conversations between parties. Each individually and collectively map to the ebBP. The ebBP schema (and technical specification) provides guidance to the CPA and messaging service regarding the processes used, the constraints expected, and the relationship that exists between the parties. Section 3.4.9.8 Change from: Figure 9 presents the relationship of the operation mappings with the ebXML architecture. If a party is capable of web services only, it can create a simple Collaboration Protocol Profile which (1) references the WSDL files that contains the appropriate concrete operations and (2) may also include the service and actions that map to the ebBP process definition. The Business Collaboration definition processed by the BSI of the ebXML capable party will use the WSDL definition to identify or initiate the corresponding web service operation invocations. Change to: Figure 9 presents the relationship of the operation mappings with the ebXML architecture. If a party is capable of web services only, it can create a simple Collaboration Protocol Profile which (1) references the WSDL files that contains the appropriate concrete operations and (2) may also include the service and actions that map to the ebBP process definition. More information is found in Section 3.5.7. The Business Collaboration definition processed by the BSI of the ebXML capable party will use the WSDL definition to identify or initiate the corresponding web service operation invocations. Appendix A: Change from: A CPA actually specifies the interface with access points defined by the business process specification used. The CPA, which may contain a reference to an ebBP definition, serves as the basis for the configuration of the BSI to enforce the protocol and semantics of the ebBP definition or, in certain cases, override such rules, as depicted in Figure 1. Change to: A CPA actually specifies the interface with access points defined by the business process specification used. The CPA, which may contain a reference to an ebBP definition, serves as the basis for the configuration of the BSI to enforce the protocol and semantics of the ebBP definition or, in certain cases, override such rules, as depicted in Figure 1. The technical specification describes in more detail the relationshp between the ebBP and the CPA. [1] With this change I also propose I ensure the first and subsequent references on CPP or CPA abbreviations are used. With the rearranging, this needs an update (where CPP and CPA are only spelled out on first reference and abbreviations used thereafter). Editorial in nature where required.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]