Hi,
I question if we need to keep partnerLinkType alive?
If we want to have a 1:1 relation of simBPEL to BPEL, then we really need to
keep it.
We think, it is good to have a more easy language, but this should be the
second step. First, there should be a bijective mapping between simBPEL and
Basically a partnerLinkType is an abstraction that names two related
portTypes, so you can then define two partnerLinks the represent each view (
i.e. roles reversed), and given two process definition somehow deduct (and
often be right) that they're related because they share a common