RE: Issue: How CPA is used in the spec

[Stefano POGLIANI <stefano.pogliani@sun.com>]

Sorry to just jump on this very late.

I understand the agreement you have reached as something like:
"if something is wrong, then the behaviour is undetermined"

Probably I misinterpret it, but I honestly would be much more
strict saying that if there is an evident conflict, an error
is delivered.

Where am I missing something ?

/stefano

» -----Original Message-----
» From: rsalz@zolera.com [mailto:rsalz@zolera.com]
» Sent: 13 March 2001 17:51
» Cc: Colleen Evans; ebXML Transport (E-mail)
» Subject: Re: Issue: How CPA is used in the spec
»
»
» Okay, here is text that hopefully addresses the comments of David's
» Fischer and Burdett:
»
» The values for the reliable messaging parameters are determined by
» appropriate elements from the CPA as identified by the optional CPAid
» element. 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. (For example, it may ignore the conflicting
» parameters, or accept some or all of them.) 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
» CPAid 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
»