ebPSS and ebMS compatibility questions

[Zvi Bruckner <zvi.b@sapiens.com>]

My questions are about using the message header elements as defined in
ebMS to implement a process defined in ebPSS.

1.  If per ebPSS a Buisness Ttansaction Activity is defined in a
Collaboration as
isConcurrent, it means that a Party can send several instances of the
request messages. Each instance will have the following identical header

proerties: Service, Action, CPAId and ConversationId.  Response messages

will also have identical properties.
How can the messaging middleware that implemets the BP identify to which

request a response belongs in order for example to check timeToPerform?

2.  If I understand correctly an Action in the header is the name of the
Requesting or Responding Business Activity.
A Responding Business Activity can include several DocumentEnvelopes for
example a PO Ack with isPositiveResponse attribute and a PO Rejection.
Both will have the same Action in the header.
How can the actual response be identified and acted upon ?
(maybe by the manifest?)

3. Since the Action should be unique per Service it means that the names
of Requesting/Responding Business Activities should be unique and this
should be explained in the ebPSS.

Zvi Bruckner