OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-cppa message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: Re: [ebxml-cppa] Timing parameter for syncReplyMode of signalsOnly


 
<hima> inline

Dale Moberg wrote:

   When we specify a syncReplyMode of signalsOnly, we are effectively overriding the business process specification which would have values for timeToAcknowledgeReceipt and timeToAcknowledgeAcceptance. (Normally, timeToAcknowledgeAcceptance would be greater than timeToAcknowledgeReceipt because extra time is required for business rules validation.) The question I have is: are we overriding timeToAcknowledgeReceipt by raising it to timeToAcknowledgeAcceptance, or are we overriding timeToAcknowledgeAcceptance by lowering it to timeToAcknowledgeRecept when we specify a syncReplyMode of signalsOnly? Do we explicitly require that timeToAcknowledgeReceipt and timeToAcknowledgeAcceptance be set to identical values whenever a syncReplyMode of signalsOnly is specified?

<hima> Bringing in the signalsAndResponse, there would be an addittional constraint
that timeToPerform should be the same as rest of these.
Do we capture all these constraints in the CPA document or once sync mode
is captured either in the BPSS layer or other flow languages, modeling
tools would take care of enforcing those constraints.
</hima>
 
 We can certainly advise tools to check that these values are equal,  as a constraint on them. I can put it in the Appendix or we canput it in the main body as a Note. action name for the bundled signals? Should we specify an action value of 'ReceiptAndAcceptanceAcknowledgment'? -ArvolaThe ebMS naming rule says that Signal service/action takes precedence over mshSignal service/action value when present,and payload service/action takes precedence over Signal, when all are present. Is there a natural interpolation for thiscase? Shall we just pick one of the Signals service/action value to fill the slot? And then let each side locally compensatefor the slightly understated service/action term? Might be easier than coining new terms for each combination.

<hima> +1
 
 Dale



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC