Re: Difference between CPP-CPA specification and BP Specificationschema

[Martin W Sachs <mwsachs@us.ibm.com>]

Chris sent me changes last night which, I believe, include addressing the
problem noted below.  They will be in the version of the TP spec that will
be sent for Public Review on or before April 23.

Regards,
Marty

*************************************************************************************

Martin W. Sachs
IBM T. J. Watson Research Center
P. O. B. 704
Yorktown Hts, NY 10598
914-784-7287;  IBM tie line 863-7287
Notes address:  Martin W Sachs/Watson/IBM
Internet address:  mwsachs @ us.ibm.com
*************************************************************************************



Karsten Riemer <Karsten.Riemer@east.sun.com> on 04/18/2001 09:12:11 AM

Please respond to Karsten Riemer <Karsten.Riemer@east.sun.com>

To:   "'ebxml-tp@lists.ebxml.org'" <ebxml-tp@lists.ebxml.org>
cc:   "'ebxml-bp-analysis@lists.ebxml.org'"
      <ebxml-bp-analysis@lists.ebxml.org>, chris.ferris@east.sun.com
Subject:  Re: Difference between CPP-CPA specification and BP Specification
      schema





I talked to Chris Ferris late last week, and he assured me that our new
spec
schema is properly reflected in the new CPP/CPA spec. I just looked at
version
0.941 that  Marty sent out, and it is still not reflected there. So just to
make sure, I re-attach the e-mail I sent out before my vacation. It has the
proper mapping. The DTD attached to  that e-mail is likely to change
slightly
for 1.0, but the role mapping should not change.

thanks,
-karsten

>Hi
>
>in the latest CPP-CPA specification Ver 9.41 line 723-745 says the
following
>
>7.4.5 Role element
>The REQUIRED Role element identifies which role in the Process
Specification
>the Party is capable of supporting via the ServiceBinding element(s)
>siblings within this CollaborationRole element.
>
>The Role element has the following attributes:
>·   a REQUIRED name attribute,
>·   a FIXED xlink:type attribute,
>·   a REQUIRED xlink:href attribute.
>
>7.4.5.1 name attribute
>The REQUIRED name attribute is a string that gives a name to the Role. Its
>value is taken from one of the following sources in the Process
>Specification[ebBPSS] that is referenced by the ProcessSpecification
element
>depending upon which element is the "root" (highest order) of the process
>referenced:
>·   initiator attribute of the binary-collaboration element,
>·   responder attribute of the binary-collaboration element,
>·   from attribute of the business-transaction-activity element,
>·   to attribute of the business-transaction-activity element,
>·   from attribute of the collaboration-activity element,
>·   to attribute of the collaboration-activity element,
>·   name attribute of the business-partner-role element.
>
><Nita>
>this requires to reflect the current [BPSS] attribute names. Moreover it
>implies that binary-collaboration may or may not be the root of a process.
>BP folks, is that so?
>
></Nita>
>
>cheers
>
>- Nita

Received: from eastmail2.East.Sun.COM (eastmail2 [129.148.1.241])      by
volcano.East.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id
BAA05763; Sat, 17 Mar 2001 01:10:24 -0500 (EST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])    by
eastmail2.East.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id
BAA06773; Sat, 17 Mar 2001 01:10:02 -0500 (EST)
Received: from one.elistx.com (one.elistx.com [209.116.252.130])  by
lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id XAA21108;      Fri, 16 Mar
2001 23:10:01 -0700 (MST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com (PMDF V6.0-24
#44856) id <0GAB00E01VPIPP@eListX.com>; Sat, 17 Mar 2001 01:08:09 -0500
(EST)
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-24 #44856)
id <0GAB00E0BVPHPJ@eListX.com> (original mail from
Karsten.Riemer@east.sun.com); Sat, 17 Mar 2001 01:08:06 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com (PMDF V6.0-24
#44856) id <0GAB00E01VPDPF@eListX.com> for ebxml-tp@elist.lists.ebxml.org
(ORCPT ebxml-tp@lists.ebxml.org); Sat, 17 Mar 2001 01:08:04 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-24
#44856) id <0GAB00E01VPDPE@eListX.com>; Sat, 17 Mar 2001 01:08:01 -0500
(EST)
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43]) by eListX.com
(PMDF V6.0-24 #44856) with ESMTP id <0GAB00BESVPCNQ@eListX.com>; Sat, 17
Mar 2001 01:08:01 -0500 (EST)
Received: from volcano.East.Sun.COM ([129.148.173.163])      by
patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id WAA13879; Fri, 16 Mar 2001
22:06:55 -0800 (PST)
Received: from karsten.lptp.East.Sun.COM (awe2-15 [129.148.2.15])      by
volcano.East.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id
BAA05737; Sat, 17 Mar 2001 01:07:15 -0500 (EST)
Date: Sat, 17 Mar 2001 00:45:57 -0500 (Eastern Standard Time)
From: Karsten Riemer <Karsten.Riemer@east.sun.com>
Subject: streamlined names in specSchema role mapping
To: ebxml-tp@lists.ebxml.org
Cc: ebxml-bp@lists.ebxml.org
Reply-to: Karsten Riemer <Karsten.Riemer@east.sun.com>
Message-id: <Roam2.0.6.984807957.21117.kriemer@volcano.east.sun.com>
MIME-version: 1.0
Content-type: multipart/mixed; boundary
="Boundary_(ID_snXeTxypJIABNgbQd2g/tg)"
Content-length: 9036
List-Owner: <mailto:ebxml-tp-help@lists.ebxml.org>
List-Post: <mailto:ebxml-tp@lists.ebxml.org>
List-Subscribe: <mailto:ebxml-tp-request@lists.ebxml.org?body=subscribe>
List-Unsubscribe: <mailto:ebxml-tp-request@lists.ebxml.org?body=unsubscribe
>
List-Archive: <http://lists.ebxml.org/archives/ebxml-tp>
List-Help: <http://lists.ebxml.org/doc/email-manage.html>, <
mailto:ebxml-tp-request@lists.ebxml.org?body=help>

Hi,
I sent Chris an updated DTD earlier this week, but as I know he was working
around the clock on a demo for London, he may not have caught these
implications.

The mapping to Roles that used to be:

initiator attribute of the binary-collaboration element
responder attribute of the binary-collaboration element
from attribute of the business-transaction-activity element
to attribute of the business-transaction-activity element
from attribute of the collaboration-activity element
to attribute of the collaboration-activity element
name attribute of the business-partner-role element

should now be:

AuthorizedRole attribute of the BinaryCollaboration  element (1st
occurrence)
AuthorizedRole attribute of the BinaryCollaboration element (2nd
occurrence)
fromAuthorizedRole  attribute of the BusinessTransactionActivity element
toAuthorizedRole attribute of the BusinessTransactionActivity element
fromAuthorizedRole attribute of the CollaborationActivity element
toAuthorizedRole attribute of the CollaborationActivity element
name attribute of the BusinessPartnerRole element

dtd attached,

-karsten