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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-bp message

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


Subject: Re: [ebxml-bp] State Alignment and Web Services


Boonserm (Serm) Kulvatunyou wrote:

>Monica, IVI WSDL attached. I can't help you technically with the WSDL. I
>hope David can.
>
>I read your quote below and am still confused. First it says "signals when
>message received for PROCESSING", then it says "business document has been
>SUCCESSFULLY processed". In my mind, if the document has been successfully
>processed the app should return business response like ConfirmBOD or AckPO
>etc., because the signal cannot precisely indicate which line items are
>successfully processed, for instance.
>  
>
mm1: We had good discussion last week in the editors' F2F which you have 
access to via the notes on Acceptance Ack and its relationship to NOF as 
well.

Work Item 39 Acceptance Acknowledgment
• Signals have technical semantics. RA is structural validation. Any 
contract formation should be part of a response. Acceptance 
Acknowledgment can include content validation.
• AA guarantees content will be or is being processed.
• Separate intent from the technical implementation.
• You can bind to attributes that are related to Receipt Acknowledgment.
• Legal community should certify technologies that are applicable for a 
specific jurisdiction.
• BPSS is a business state alignment protocol.

Note that we, at least now, we say will or is being processed, not 
successfully processed. That I believe would be involved with the 
response. Even in the v1.1, the response is substantive and infer an 
action against that processing completion. Does this answer your 
question? Thanks.



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