TP requirements for BP

[Karsten Riemer - Sun IR Development <Karsten.Riemer@East.Sun.COM>]

I am sending this to just the limited metamodel list, because I have not heard 
back from any of the TP team yet, but want to start discussing this in today's 
meeting.

-karsten

------------- Begin Forwarded Message -------------

Date: Tue, 24 Oct 2000 11:11:24 -0400 (EDT)
From: Karsten Riemer - Sun IR Development <kriemer@volcano.East.Sun.COM>
Subject: TP requirements for BP
To: ebxml-tp@lists.ebxml.org
Cc: kriemer@volcano.East.Sun.COM
MIME-Version: 1.0
Content-MD5: l6RXJkG1jy26+VrA+1ZC5w==

Hi,
In preparation for the 12 noon BP/CC metamodel meeting today I have put the 
following list together of possible TP requirements for BP:

In general I am intending to present the following as TP background to BP team:

CPP is the advertisement of capability.
CPA is the mutual commitment

Functional (business) content of TPP:

What are the business collaborations supported?
What are the service transactions supported within each business collaboration?
For each service transaction:
  What type of contract is it governed by? (link to REA)
  What are the entry conditions (pre-conditions), stated as prior completion 
  of other service transactions, or specifically prior completed contracts or 
  economic events?
  What is the initiating message?
  What are the possible response messages?
For each possible response message:
  What is the exit conditions (post conditions), stated as resulting completion,
  partial completion, or failure of the service transaction, or specifically the
  resulting contract, economic event, or exception condition?
  Optionally, what service transaction do I expect to be initiated next,
  following this particular response message?
  
IN terms of requirements of TP for BP, I have identified the following, but need 
your comments, additions, corrections:

1. TP is all XML, therefore BP must make it possible to extract in XML format 
all the pieces of information that are specified as part of BP but required as 
part of a CPP or CPA.
2. TP supports thin or thick versions of CPP and CPA. Therefore:
  2.a. For thin version, BP must provide XML documents with distinct ID 
referenceable:
    2.a.1. Business Collaborations
    2.a.2. Commercial Transactions (or "service transactions")
    2.a.3. Technical handshake patterns.
  2.b. For thick version BP and TP must use the same expression and structure 
for the shared part of definitions of
    2.b.1   business collaboration
    2.b.2. Commercial Transactions (or "service transactions")
    2.c.3. Technical handshake patterns.
3.  Since CPP is a subset of a BP definition, defining partner capabilities, 
there must be a way of subsetting:
   3.a.  Enabled service transactions within a business collaboration
   3.b.  Enabled responses within a service transaction
4.  Since CPA is a concise commitment, there must be a way of subsetting and 
overriding parameters of the BP definition, e.g. make optional mandatory or vice 
versa, override time-outs, etc.

Comments, additions, corrections?

-karsten





---------------------------------------------------
Karsten Riemer,
Director, Information Architecture,
Enterprise Management Architecture Group
Sun Microsystems Inc.,
MailStop UBUR03-313
1 Network Drive,
Burlington, MA 01803-0903

ph. 781-442-2679
fax 781-442-1599
e-mail karsten.riemer@sun.com


------------- End Forwarded Message -------------


---------------------------------------------------
Karsten Riemer,
Director, Information Architecture,
Enterprise Management Architecture Group
Sun Microsystems Inc.,
MailStop UBUR03-313
1 Network Drive,
Burlington, MA 01803-0903

ph. 781-442-2679
fax 781-442-1599
e-mail karsten.riemer@sun.com