RE: [ebxml-dev] CPA example

[Arvola Chan <arvola@tibco.com>]

Please see comments bracketed by <arvola> </arvola>.

-----Original Message-----
From: Keith Babo [mailto:keith.babo@sun.com]
Sent: Tuesday, March 19, 2002 2:46 PM
To: ebxml-dev@lists.ebxml.org
Subject: [ebxml-dev] CPA example



I have a quick question on the structure of the
draft-cpa-example-015.xml document (which I grabbed from the ebxml-cpa
archive list).  It appears as though "Purchase Order Request Action" is
defined twice under CanSend elements; once for a synchronous delivery
channel, and once for an asynchronous delivery channel.  Is this right??

<arvola>
Yes, that is correct.
</arvola>

My understanding was that a given action could only appear once within
a CanSend element under a given Party.

The 1.09 spec has this to say on the matter (pg. 34, line 1316) :

Under a given PartyInfo element and among all subordinate CanSend
elements, there SHALL be only one ThisPartyActionBinding element whose
action attribute has a given value.

Is this an error in the example CPA, or am I just missing something?

<arvola>
The above constraint has been removed. Section 8.4.12 in the 1.10 draft now
says:

"Under a given ServiceBinding element, there MAY be multiple CanSend or
CanReceive child elements with the same action to allow different software
entry points and Transport options. In such a scenario, the DeliveryChannels
referred by the ChannelID child elements of ThisPartyActionBinding SHALL
point to distinct EndPoints for the receiving MSH to uniquely identify the
DeliveryChannel being used for this particular message exchange."
</arvola>

 The following is excerpted from the example CPA document :

cheers,
keith

<tp:CollaborationRole tp:id="Buyer">

            <tp:ProcessSpecification tp:version="2.0"
tp:name="PIP3A4RequestPurchaseOrder" xlink:type="simple"
xlink:href="http://www.rosettanet.org/processes/3A4.xml"
tp:uuid="urn:icann:rosettanet.org:bpid:3A4$2.0"/>

            <tp:Role tp:name="Buyer" xlink:type="simple"
xlink:href="http://www.rosettanet.org/processes/3A4.xml#Buyer"/>

            <tp:ApplicationCertificateRef tp:certId="CompanyA_AppCert"/>

            <tp:ServiceBinding>

                <tp:Service>bpid:icann:rosettanet.org:3A4$2.0</tp:Service>

                <tp:CanSend>

                    <tp:ThisPartyActionBinding tp:id="companyA_ABID1"
tp:action="Purchase Order Request Action"
tp:packageId="CompanyA_RequestPackage">

                        <tp:ActionContext tp:binaryCollaboration="Request
Purchase Order" tp:businessTransactionActivity="Request Purchase Order"
tp:requestOrResponseAction="Purchase Order Request Action"/>

                        <tp:ChannelId>asyncChannelA1</tp:ChannelId>

                    </tp:ThisPartyActionBinding>


<tp:OtherPartyActionBinding>companyB_ABID4</tp:OtherPartyActionBinding>

                </tp:CanSend>

                <!-- The next binding uses a synchronous delivery
channel -->

                <tp:CanSend>

                    <tp:ThisPartyActionBinding tp:id="companyA_ABID6"
tp:action="Purchase Order Request Action"
tp:packageId="CompanyA_RequestPackage">

                        <tp:ActionContext tp:binaryCollaboration="Request
Purchase Order" tp:businessTransactionActivity="Request Purchase Order"
tp:requestOrResponseAction="Purchase Order Request Action"/>

                        <tp:ChannelId>syncChannelA1</tp:ChannelId>

                    </tp:ThisPartyActionBinding>


<tp:OtherPartyActionBinding>companyB_ABID6</tp:OtherPartyActionBinding>

                    <tp:CanReceive>

                        <tp:ThisPartyActionBinding tp:id="companyA_ABID7"
tp:action="Purchase Order Confirmation Action"
tp:packageId="CompanyA_SyncReplyPackage">

                            <tp:ActionContext
tp:binaryCollaboration="Request Purchase Order"
tp:businessTransactionActivity="Request Purchase Order"
tp:requestOrResponseAction="Purchase Order Confirmation Action"/>

                            <tp:ChannelId>syncChannelA1</tp:ChannelId>

                        </tp:ThisPartyActionBinding>


<tp:OtherPartyActionBinding>companyB_ABID7</tp:OtherPartyActionBinding>

                    </tp:CanReceive>

                    <tp:CanReceive>

                        <tp:ThisPartyActionBinding tp:id="companyA_ABID8"
tp:action="Exception" tp:packageId="CompanyA_ExceptionPackage">

                            <tp:ChannelId>syncChannelA1</tp:ChannelId>

                        </tp:ThisPartyActionBinding>


<tp:OtherPartyActionBinding>companyB_ABID8</tp:OtherPartyActionBinding>

                    </tp:CanReceive>

                </tp:CanSend>

            </tp:ServiceBinding>

        </tp:CollaborationRole>





----------------------------------------------------------------
The ebxml-dev list is sponsored by OASIS.
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.ebxml.org/ob/adm.pl>