Fwd: Re: [ebxml-cppa] Issue MUST use OtherPartyActionBinding in CPAs (or CPA templates)

[Martin Sachs <msachs@cyclonecommerce.com>]

Consider the following improved version of my previous
suggestion:

The OtherPartyActionBinding element is REQUIRED in CPAs and

CPA templates and SHALL NOT be used in a CPP.

Regards,
Marty

Date: Mon, 29 Sep 2003 20:47:03 -0400
To: Dale Moberg <dmoberg@cyclonecommerce.com>
From: Martin Sachs <msachs@cyclonecommerce.com>
Subject: Re: [ebxml-cppa] Issue MUST use OtherPartyActionBinding in CPAs (or CPA templates)
Cc: "ebxml-cppa@lists.oasis-open.org" <ebxml-cppa@lists.oasis-open.org>

The proposed fix should work.  However instead, I prefer these words for the first sentence:

The OtherPartyActionBinding element is REQUIRED in CPAs and

CPA templates.

In the second sentence of the first paragraph, please also replace "PartyInfo" by "PartyInfo element".

Regards,
Marty

At 09:08 AM 9/29/2003 -0700, Dale Moberg wrote:

Issue: MUST use OtherPartyActionBinding in CPAs and CPA templates

The 2.0 specification section 8.4.13 says:

The OtherPartyActionBinding element is only used in the case of CPAs.
It is of type IDREF and identifies a matching ThisPartyActionBinding
element
that is found under the collaboration partner's PartyInfo. It indirectly

identifies the DeliveryChannel the other Party will use for sending or
receiving the action message in question and the expected Packaging.
Within a CPA and under the same CanSend or CanReceive element, the
DeliveryChannels and Packaging used/expected by the two Parties,
as indicated by the ThisPartyActionBinding and OtherPartyActionBinding
elements,
MUST be compatible.


Implementers have found this paragraph to be unclear that the
OtherPartyActionBinding must be used in CPAs (and CPA templates).
Can code assume that in a CPA or CPA template an OtherPartyActionBinding
will be present?

Proposed clarification is to change the first sentence to read:

The OtherPartyActionBinding element is only used in the case of CPAs and
CPA templates, and MUST be present in those cases.


To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/ebxml-cppa/members/leave_workgroup.php.

*************************************
Martin Sachs
standards architect
Cyclone Commerce
msachs@cyclonecommerce.com

*************************************
Martin Sachs
standards architect
Cyclone Commerce
msachs@cyclonecommerce.com