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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-cppa-negot message

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


Subject: Re: [ebxml-cppa-negot] BPSS loose ends


Marty,

I think all these loose ends are included as comments
in the latest specification and my response which I sent
a few minutes back should have dealt with them. 

Please let me know if I've missed anything else.
Corresponding CPA changes to add new simple parts are 
the missing pieces...

-thanks
hima

Martin W Sachs wrote:
> 
> I believe that the following are still open matters for the negotiation
> BPSS.  Please comment.
> 
> Two of the the business document names contain the characters "DOC" in the
> value of the name attribute and "doc" in the value of the nameId attribute.
> They are "CPA Final Response DOC/doc" and "CPA Final Response DOC/doc
> Signed".  This is not necessarily a problem but if comparisons of text
> strings are case-sensitive, it could cause some confusion or programming
> errors. It would be better to use "doc" in both the name and the nameId
> attribute as is the case with  all the other business documents.
> 
> There are no condition tests for rejection conditions in the exchange of
> the final CPAs. Reasons can include:
> - The final CPA does not agree with the recipient's understanding of what
> should be in it (some kind of state-tracking mismatch).
> - The final CPA was not signed although signing was agreed to.
> - The signature on the final CPA cannot be validated.
> - The second signature on the double-signed CPA cannot be validated.
> - An acknowledgment was received when a double-signed CPA was expected.
> 
> The "CPA Final Response doc" document is used for both acceptance and
> reject. Except for this case, a message receipient can determine success or
> failure from the business document name in the message.  For "CPA Final
> Response doc"  we need a separate success/failure indicator in the message,
> that indicator has to be checked, and handling of the condition is outside
> the choreography.
> 
> Regards,
> Marty
> *************************************************************************************
> 
> Martin W. Sachs
> IBM T. J. Watson Research Center
> P. O. B. 704
> Yorktown Hts, NY 10598
> 914-784-7287;  IBM tie line 863-7287
> Notes address:  Martin W Sachs/Watson/IBM
> Internet address:  mwsachs @ us.ibm.com
> *************************************************************************************
> 
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>


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


Powered by eList eXpress LLC