Re: [ebxml-cppa] Important: procedure for revisions leadingtoCPPAversion 1.1

[Arvola Chan <arvola@tibco.com>]

Hima:

 

Your examples exactly match my intent for the ActionContext element. I was trying to take a short cut and represent the hierarchy of CollaborationActivity names as an ordered sequence of CollaborationActivity elements. An alternate representation would be to treat CollaborationActivity as recursive element with an optional nested CollaborationActivity sub-element.

 

We can change the schema as follows:

 

Previous Definition

 

 <element name="ActionContext">
  <complexType>
   <sequence>
    <element ref="tns:CollaborationActivity" minOccurs="0" maxOccurs="unbounded"/>
   </sequence>
   <attribute name="binaryCollaboration" type="tns:non-empty-string" use="required"/>
   <attribute name="businessTransactionActivity" type="tns:non-empty-string" use="required"/>
   <attribute name="requestOrResponseAction" type="tns:non-empty-string" use="required"/>
  </complexType>
 </element>
 <element name="CollaborationActivity" type="tns:non-empty-string"/>
 <element name="CollaborationRole">
  <complexType>
   <sequence>
    <element ref="tns:ProcessSpecification"/>
    <element ref="tns:Role"/>
    <element name="DefaultSigningCertificateRef" type="tns:CertificateRef.type" minOccurs="0"/>
    <element ref="tns:ServiceBinding" maxOccurs="unbounded"/>
   </sequence>
   <attribute ref="tns:id"/>
  </complexType>
 </element>

 

Revised Definition

 

 <element name="ActionContext">
  <complexType>
   <sequence>
    <element ref="tns:CollaborationActivity" minOccurs="0"/>
   </sequence>
   <attribute name="binaryCollaboration" type="tns:non-empty-string" use="required"/>
   <attribute name="businessTransactionActivity" type="tns:non-empty-string" use="required"/>
   <attribute name="requestOrResponseAction" type="tns:non-empty-string" use="required"/>
  </complexType>
 </element>
 <element name="CollaborationActivity">
  <complexType>
   <sequence>
    <element ref="tns:CollaborationActivity" minOccurs="0"/>
   </sequence>
   <attribute name="name" type="tns:non-empty-string"/>
  </complexType>
 </element>

 

Regards,

-Arvola

-----Original Message-----
From: Himagiri(Hima) Mukkamala <himagiri@sybase.com>
To: Arvola Chan <arvola@tibco.com>
Date: Thursday, December 13, 2001 6:11 PM
Subject: Re: [ebxml-cppa] Important: procedure for revisions leading toCPPAversion 1.1

This would be the alternate to XPath and I'm fine with this.
Only problem is the CollaborationActivity names which are repeating
have to be heirachial. So would CollaborationActivity element
be a recursive element so that we could say

If using a BC with named "BC" which has a CollaborationActivity "CA1"
which has a BusinessTransactionActivity "BTA1" with a requestingBusinessActivity
of "RBA1"

BCName=BC,CAName=CA1(BTAName=BTA1),RBAName=RBA1

or if it could have an internal CollaboratoinActivity

BCName=A,CAName=CA1(CAName=CA2(BTAName=BTA1)),RBAName=RBA1

If the CollaborationAcivity names could be expressed in a heirachial fashion
using the schema, I'm ok with that or else we could go with something
like LDAP naming heirarchy and have just one attribute for the whole thing

-hima

Arvola Chan wrote:

 Hima: Yes, the ActionContext element is intended to convey the long action name. At one point, we agreed that the hierarchical path name of an action can be completely characterized by the top level BinaryCollaboration name, any number of CollaborationActivity name(s), a BusinessTransactionActivity name, plus either a RequestingBusinessActivity name or a RespondingBusinessActivity name. The BinaryCollaboration name, BusinessTransactionActivity name, RequestingBusinessActivity name or RespondingActivity name are captured by the corresponding attributes in the ActionContext element. The potentially repeating Collaboration Activity name(s) can be stored in the CollaborationActivity element (minOccurs="0" maxOccurs="unbounded"). Regards,-Arvola

-----Original Message-----
From: Himagiri(Hima) Mukkamala <himagiri@sybase.com>
To: Arvola Chan <arvola@tibco.com>
Date: Thursday, December 13, 2001 5:32 PM
Subject: Re: [ebxml-cppa] Important: procedure for revisions leading toCPPAversion 1.1
 Hi Arvola,

I was hoping to either extend the ActionBinding to add the short
and longnames. What's the significance of ActionContext
under the ActionBinding. I see that it has Collaboration,
TransactionActivityName. Was the intent to use this
element for conveying the long action name

-hima

Arvola Chan wrote:

Tony: I plan to submit the following changes by December 21:

1. Updated schema
2. Updated CPP example
3. Updated CPA example
4. BPSS example as referenced from CPP/CPA
5. Description of Reliable Messaging parameters
6. Description of synchronous reply modes
7. Description of ActionBinding
8. Changes to Packaging to accommodate synchronous response

Since these changes are going to be rather pervasive, I would like to submit an updated Word document with change tracking enabled. By the way, I am using Microsoft Word 2000. Regards,-Arvola

-----Original Message-----
From: Tony Weida <rweida@hotmail.com>
To: ebxml-cppa@lists.oasis-open.org <ebxml-cppa@lists.oasis-open.org>
Date: Thursday, December 13, 2001 10:05 AM
Subject: [ebxml-cppa] Important: procedure for revisions leading to CPPAversion 1.1
 The attached document briefly describes procedures and initial schedules for submitting changes to the CPPA specification as agreed during today's teleconference. Tony Weida