[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [ebBP] 5/2/2004: [RSD] Informal Meetings with ebXML IIC, WS-CAF,CPPA and Reg/Rep
iscussion|OASIS.ebBP.Symposium Informal TC Meetings;
Topic|;
Point|Notes and Actions Recommended for Team Consideration;
mm1@
We had some productive sessions with: WS-CAF, ebXML CPPA, and ebXML IIC.
I would propose we follow through to realize these opportunities as we
make improvements for v2.0 and lay the groundwork for expanded
functionality in v3.0 (as well as align with the loosely coupled, highly
aligned set of ebXML specifications). In addition, we will likely
require a collaborative meeting with ebMS, CPA and IIC in the nearer-term:
* WS-CAF (29 April 2004)
o For WS-CAF: WS-CAF can handle shared activity and protocol.
Could map to business level activities and provide a context
data structure [1]. With WS-CAF, shared persistence can be
managed. WS-CAF can support multiple contexts as well as
hierarchical composition. WS-CAF doesn't constrain design
choices. In the most recent WS-CAF evolving draft the
Activity Lifecycle Service (ALS) has become an
implementation detail.
+ WS-CAF could enable creation of links between binary
and multi-party collaorations and use of different
contexts as well as those in an overreaching
collaboration activity.
o For BPSS, could reference a URL to the context service.
Identify relationship between application and infrastructure.
o Discussion Items and Actions.
+ Set up another followup meeting with WS-CAF after
their draft is released. ebBP has provided one of the
few use cases not related to transactions and security
usage for late May-June 2004.
+ Discussion items
# Investigate how WSDL support in ebBP relates to
defiinitions in WS-CAF. Determine how this fits
with WS-CAF definitions of context, coordination
and transactional services.
# Determine how to map ebBP activities onto WS-CAF
activities.
# Understand how to generalize signals to cover
potential usage of context, coordination and
transaction servers.
[1] WS-CAF looks at activities relevant to the executable environment.
* ebXML IIC (29 May 2004):
o Discussed the use of fork-join semantics in BPSS and its
reuse in IIC. Discussed briefly BusinessStateLink and
BusinesStateLinkType on the BTA and BC. These type semantics
can be used by IIC for thread control (serialization), block
or units (with changes in Transition proposed by Dale)
[hybrid activity execution and unit composition] and fork-join.
o Discussion Items and Actions:
+ Provide IIC the draft schema to review and understand
in the context of:
# BPSS testing
# Use of BPSS constructs for the test framework
process
# Use of BPSS constructs to support workflow
semantics in the test framework
+ Review of BPSS use cases to map against test framework
functionality.
o Set up follow-up sessions to discuss:
+ Use of BPSS constructs (late May-June 2004)
# To support workflow semantics in test framework
# For the test framework that is in itself a process
+ Future plans for BPSS testing (Summer 2004 when ebBP
v2.0 is nearing completion)
# Identify definition of and usage of QoS
attributest to assist IIC in differentiating
outcomes that occur in business transactions in
BPSS particularly isPositiveResponse and
NegativeReceiptAcknowledgement.
# Perhaps ebBP could learn from test framework
experience and potential need for pre-post
conditions and their use in test process execution.
# ebXML IIC is yet another user of ebBP (and may
be able to assist in defining if monitoring
through ebBP could support test execution and
visibility).
* ebXML CPPA (28 April 2004)
o CPA negotiation and BPSS effectively used in a research
project (for thesis) by Sacha Schlegel. Created BSI and
handed it the BPSS instance, NDD and CPA template (created
from composition process). Allows to create CPA template.
Execute negotiation business process. Showed the human as
the negotiation algorithm.
+ Negotiation could be packaged as a service (which
encourages use of ebBP to support that service).
o Discussion Items and Actions
+ CPPA v2.1 will align with ebBP v.2.0 via work by
Schlegel, Moberg particularly.
+ Extend CPA negotiation and CPA to support other
process specifications. Requires ebBP alignment (WI-12
WSDL Support [v2.0 and v3.0] and WI-20 Use of other
Business Transaction protocols [v3.0].
+ CPPA changes to support BPSS:
# Role values and action context (to be determined
on latter).
# Added Process Specification and
ProcessSpecificationHead (that allows some
abstraction options in CPA)
# Provide extensibility of CollaborationRole (to
support our composition-binding aspects of Role
in ebBP) and DocumentExchange.
+ Open items:
# How to differentiate BPSS business signals and
messages if WSDL is used. How does this affect
exceptions?
# Resolve action context questions between ebBP,
ebMS and CPPA.
# Resolve conversational semantics and impacts
from ebMS projected v3.0 and CPA v3.0.
+ ACTIONS:
# Set up meeting with ebMS and CPA for June 2004
on open items. [2]
# Set up meeting with CPA on negotiation as a
service in June / July 2004.
* Other:
o Reg/Rep (29 April 2004): With the future use of event
notification and potential use of the registry for storage
of business processes, fragments and activities, we need to
talk about difference between entity/object and process
activities and states, and their synergy and dependencies,
and collaboration composition. v3.0 item.
o ebSOA (29 April 2004): There was quite a bit of discussion
regarding business process in ebSOA meeting. I believe we
need more discussion to clarify what ebBP does and its role
in the larger BPM space. v3.0 item. [2]
[2] I would suggest this be discussed first in the ebXML JC where we can
provide visibility to this coordination item.
All-in-all a good set of sessions. In addition, we received a good
response from our brief at the OASIS symposium on Monday and throughout
the week. We have interest in at least three major industries for ebBP -
automotive, high-technology, and financial services (including use of
other complementary evolving technologies). I encourage your comments on
these meetings and opportunities.
@mm1
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]