RE: Issue: How CPA is used in the spec

["Burdett, David" <david.burdett@commerceone.com>]

Rich, you're spot on. I can live with it for the purposes of QR review as we
are out of time although there is a small typo in that "CPA" in the last
sentence should be "CPAId". 

However I'd appreciate your views on adding a final sentence which says ...
"A receiver MAY choose to use the parameters in the header to over-ride the
parameters in the CPA."

David

-----Original Message-----
From: Rich Salz [mailto:rsalz@zolera.com]
Sent: Monday, March 12, 2001 5:33 PM
To: Colleen Evans
Cc: ebXML Transport (E-mail)
Subject: Re: Issue: How CPA is used in the spec


> Could one of you involved in this thread (Chris, David, Rich or Maryann)
> please send me the finalized wording to be incorporated into the spec once
> you've agreed.  Your emails are crossing and I'm not sure at this point
> what has been agreed to or by whom.

My fault, primarily, for responding too quick off the mark without
supplying any context.

Here is what I believe the text should be; I'm fairly sure Chris and
Maryann will concur, and David is likely to be "can live with it."

The values for the reliable messaging parameters are determined by
appropriate elements from the CPA identified by the CPAid. If a receiver
determines that a message is in conflict with the specified CPA, the
appropriate handling of this conflict is undefined by this
specification. Therefore, senders SHOULD NOT generate such messages
unless they have prior knowledge about the receiver's capability to deal
with this conflict.

If a receiver chooses to generate an error as a result of a detected
inconsistency, then it MUST report it with an errorCode of Inconsistent
and a severity of Error. If it chooses to generate an error because the
CPA is not recognized, then it MUST report it with an error code of
NotRecognized and a severity of Error.

------------------------------------------------------------------
To unsubscribe from this elist send a message with the single word
"unsubscribe" in the body to: ebxml-transport-request@lists.ebxml.org