RE: Issue: How CPA is used in the spec

[David Fischer <david@drummondgroup.com>]

Very good, and I like your analogies on the next message...

David Fischer
-----Original Message-----
From: rsalz@zolera.com [mailto:rsalz@zolera.com]
Sent: Wednesday, March 14, 2001 9:22 AM
To: Colleen Evans
Cc: ebXML Transport (E-mail)
Subject: Re: Issue: How CPA is used in the spec


Okay, then the following seems accurate.
	The CPAId element identifies the governing CPA if one exists.

[ Separate discussion:  how does a receiver know if the CPAid refers to
a CPA, or if it's an arbitrary handle being used for, e.g., bootstrap? ]

So, here's the final text, for the third time.

If the parties are operating under a CPA, then the reliable messaging
parameters are determined by the appropriate elements from that CPA, as
identified by the CPAId element.

If a receiver determines that a message is in conflict with the 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
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