Groups - Weekly ebBP Teleconference Call modified

[monica.martin@sun.com]

Weekly ebBP Teleconference Call has been modified by Monica Martin (monica.martin@sun.com).

Date:  Monday, 08 March 2004
Time:  12:00pm - 01:00pm Pacific Time

Event Description:
866 882 3998
International 865 525 0769
9081038

12 noon PST
1 p.m. MST
3 p.m. EST
8 p.m. BST
9 p.m. CET
4 a.m. Taipei, Perth Tuesday
5 a.m. Tokyo, Tuesday
7 a.m. Sydney, Tuesday

At time of close of vote on weekly calls, updated time will be posted (status as of 26 Feb 2004).

Agenda:
8 March 2004:
1. Approval of 23 Feb 2004 Meeting Minutes.
2. Overview of existing work items for final discussion and notification of vote (to begin week of 8 March 2004):

7 Versioning
12 WSDL 
22 Business transaction pattern support
13-25-26 Role binding
28 Role changes
43 Name and NameID (ID and IDREF)
55 Late binding / TTP for v2.0

3. Complete discussion on context mechanism proposal from Webber.


Reference summary list posted http://www.oasis-open.org/archives/ebxml-bp/200402/msg00250.html


Minutes:
ebBP TC Teleconference Call 23 Feb 2004

Present:
Dodds
Fischer
Kartha
Krishnan
Moberg
Nagahashi
Roberts
St. Amand
Tell
Webber
Martin

Guest: 
Bill McCarthy

Excused/travel:
Dubray

Agenda:

    1. Approval of meeting minutes, 16 Feb 2004.

Quorum reached at the meeting.
No objections on acceptance.

    2. Finalize transaction patterns discussion, Roberts.

Uploaded schema.
Roles proposal included as well as some inclusion of BT patterns
Have not uploaded new changes with BT patterns. There was some confusion between the R10 description and model views. Bus Transaction element will remain. Six additional elements will be part of substitution groups that represent UMM R10 core business transaction
patterns. Fields would be default values that can be overridden.
Martin: See email sent.

Reference: http://www.oasis-open.org/archives/ebxml-bp/200402/msg00236.html (R10 Question)
Schema uploaded by Roberts: http://www.oasis-open.org/archives/ebxml-bp/200402/msg00240.html

Roberts: Will correct and post tables with schema changes.
Martin: Put actual namespace.

    3. If ready, signals discussion, Roberts and Mukkamala.

Reference: See above.

Roberts: Signal section is optional. If you use a different transport, like RNIF, you may have signal content restrictions. Signals can be overriden at agreement time which may affect CPA. 
Moberg: Understood.
Roberts: Similar to time. The BT patterns should be referenced by the signal to see where it fits. If you don't have a reference, and it is used, what happens? Think that TT Ack Acceptance is not available if the pattern has that set to No.
Martin: Could that be the same alternate channel case you had for a request?
Roberts: This could infer two different responses: Do you care if there is a receipt or is it that you do not want a receipt? Need to define what we understand what the BT patterns mean. Implied logic exists for business transaction patterns.
Martin: Change of name for isLegallyBinding.
Tell: For v3.0, if entering into this agreement in good faith, may need to ask the other party why you did or didn't receive a signal. This is part of contract law.
Martin: What would that require?
Tell: If you don't get your receipt, the electronic record is treated as unsent. 
Martin: Does that differ for a signal or a message?
Tell: Unsure but may be both.

Reference: Indian 2000 Information Act

Roberts: Don't believe there will be conflicts with Mukkamala.
Do we override the transaction recognizing we reference patterns elsewhere?
Tell: From a TPA, it is important to know what technical feature implements a part of the agreement. For example, is it ebMS acknowledgement or ReceiptAck?
Webber: When you create a signal, you point to a specification, correct?
Roberts: No it is a reference to a schema file such as a CAM template. 
Moberg: On Tell comment, agree this is a v3.0 feature - asking questions about failure of a signal. Like a reminder (good faith).
Martin: Reference BCP  - warning on Responder's expectation of a Receipt Ack that does not occur.
Tell: Could occur on both sides. It depends on business semantics and trade practices.

Roberts: Post.
See reference above for schema posted 23 Feb 2004.

    4. CBPC brief, Nita Sharma and William McCarthy.

Martin: Want to discuss reusable elements of BPSS that are relevant to CBPC.
Moberg: Relate to modularity of BPSS specification - package construct.
WSDL uses many imports and includes. For use of a catalog in a registry, we may need to think about WSDL structure and pulling in reusable elements and references. We don't currently have that mechanism in BPSS, do we?
Roberts: There is an include mechanism in BPSS. 

Reference: Include element for ProcessSpecification and Package
(v1.1, v1.05)

Moberg: Need to revisit this to support catalog concepts in the package discussion (and use of ID and IDREF). What are their physical realization as it relates to CBPC in a registry?
Martin: Need to understand business domain constraints as well as RIM/storage/metadata requirements for artifacts.
Webber: Look at Registry SCM SC may provide input as well. 
Tell: Included CBPC in my BusinessPartnerType and Roles diagram. This effectively integrates ebBP and CBPC.

Reference: http://www.oasis-open.org/archives/ebxml-bp/200402/msg00239.html

    5. Context management proposal by David Webber (if time allows).

Webber: Strawman document provided. Wants to avoid two distinct ways of handling context. What way do we point - BPSS, CPPA and context? Using XML 1.0 as a basis. Open source CAM processor was done by Martin Roberts.
Roberts: Need to get Keith Swenson on the call 8 March 2004. Favors approach that allows context to be done outside
of BPSS. What are the linkages between the CPPA, context and the BPSS? Starting the BPSS as a design tool, that can be overridden outside of it is technically a better approach. There are four lifecycles that would be affected by late binding.
Tell: The idea of binding outside of BPSS works some times. One should not design for ad hoc bindings, with a generic mechanism. Feel we should work on model first and its semantics. Revert to external if not capable with model.
Roberts: Extend to help with overridding time and provide capability to provide additional parameters to be able to validate a business document. This capability doesn't exist in CPPA. Relevant to:

1. Business document content
2. Context affect on process or the actual timing or pointers to document names
3. CPPA locks all those three together.

Tell: Don't need to include CAM into BPSS then.
Roberts: Agree.
Tell: Have a proposal soon to equate BPSS with Core Components. Had a long discussion with Fred van Blommestein to do the same constructs for BPSS that exist in CCTS.
Roberts: A URL for context could be used if no CPPA was available.
Tell: Don't think we can point to something we don't know about.
Roberts: There are competiting technologies.
Tell: This uncovers dangers with a generic mechanism. For example, if you want to extend by restriction (data type). A generic mechanism you can violate basic rules of the process specification semantics.

Continue discussion 8 March 2004.

Other business:
a. Draft white paper proposal for comment and vote.
No time to discuss.

b. Ask to defer meeting 1 March 2004 due to dual European travel conflicts. Reconvene 8 March 2004.
No objections from members present (quorum).

WI 12: Deferred for a short time to get new proposal.

ACTIONS: 
MARTIN: SEND OUT UPDATE SUMMARY ON EXISTING WORK ITEM PROPOSALS FOR DISCUSSIONS AND VOTES TO OCCUR THROUGH 15 MARCH 2004.
DONE.
MARTIN: SEND OUT NOTICE RE: WHITE PAPER PROPOSAL. DONE 26 FEB 2004.
TEAM: REVIEW XSD FROM ROBERTS. POSTED 23 FEB 2004.
MARTIN: SET UP DISCUSSION SESSION WITH CBPC IN BONN AS A FOLLOWUP TO THIS DISCUSSION. DONE, DISCUSSED WITH PROJECT LEAD
26 FEB 2004. FOLLOW-UP FOR BONN.
MARTIN: SET UP COMPLEMENTARY DISCUSSION WITH REGISTRY SCM FOR CBPC AND BP. DONE 26 FEB 2004.

This event is one in a list of recurring events.
Other event dates in this series:

Monday, 12 January 2004, 12:00pm to 01:00pm Pacific Time
Monday, 19 January 2004, 12:00pm to 01:00pm Pacific Time
Monday, 26 January 2004, 12:00pm to 01:00pm Pacific Time
Monday, 02 February 2004, 12:00pm to 01:00pm Pacific Time
Monday, 09 February 2004, 12:00pm to 01:00pm Pacific Time
Monday, 16 February 2004, 12:00pm to 01:00pm Pacific Time
Monday, 23 February 2004, 12:00pm to 01:00pm Pacific Time
Monday, 01 March 2004, 12:00pm to 01:00pm Pacific Time
Monday, 15 March 2004, 12:00pm to 01:00pm Pacific Time
Monday, 22 March 2004, 12:00pm to 01:00pm Pacific Time
Monday, 29 March 2004, 12:00pm to 01:00pm Pacific Time
Monday, 05 April 2004, 12:00pm to 01:00pm Pacific Time
Monday, 12 April 2004, 12:00pm to 01:00pm Pacific Time
Monday, 19 April 2004, 12:00pm to 01:00pm Pacific Time
Monday, 26 April 2004, 12:00pm to 01:00pm Pacific Time
Monday, 03 May 2004, 12:00pm to 01:00pm Pacific Time
Monday, 10 May 2004, 12:00pm to 01:00pm Pacific Time
Monday, 17 May 2004, 12:00pm to 01:00pm Pacific Time
Monday, 24 May 2004, 12:00pm to 01:00pm Pacific Time
Monday, 31 May 2004, 12:00pm to 01:00pm Pacific Time
Monday, 07 June 2004, 12:00pm to 01:00pm Pacific Time
Monday, 14 June 2004, 12:00pm to 01:00pm Pacific Time
Monday, 21 June 2004, 12:00pm to 01:00pm Pacific Time
Monday, 28 June 2004, 12:00pm to 01:00pm Pacific Time
Monday, 05 July 2004, 12:00pm to 01:00pm Pacific Time
Monday, 12 July 2004, 12:00pm to 01:00pm Pacific Time
Monday, 19 July 2004, 12:00pm to 01:00pm Pacific Time
Monday, 26 July 2004, 12:00pm to 01:00pm Pacific Time
Monday, 02 August 2004, 12:00pm to 01:00pm Pacific Time
Monday, 09 August 2004, 12:00pm to 01:00pm Pacific Time
Monday, 16 August 2004, 12:00pm to 01:00pm Pacific Time
Monday, 23 August 2004, 12:00pm to 01:00pm Pacific Time
Monday, 30 August 2004, 12:00pm to 01:00pm Pacific Time
Monday, 06 September 2004, 12:00pm to 01:00pm Pacific Time
Monday, 13 September 2004, 12:00pm to 01:00pm Pacific Time
Monday, 20 September 2004, 12:00pm to 01:00pm Pacific Time
Monday, 27 September 2004, 12:00pm to 01:00pm Pacific Time
Monday, 04 October 2004, 12:00pm to 01:00pm Pacific Time
Monday, 11 October 2004, 12:00pm to 01:00pm Pacific Time
Monday, 18 October 2004, 12:00pm to 01:00pm Pacific Time
Monday, 25 October 2004, 12:00pm to 01:00pm Pacific Time
Monday, 01 November 2004, 12:00pm to 01:00pm Pacific Time
Monday, 08 November 2004, 12:00pm to 01:00pm Pacific Time
Monday, 15 November 2004, 12:00pm to 01:00pm Pacific Time

View event details:
http://www.oasis-open.org/apps/org/workgroup/ebxml-bp/event.php?event_id=3545

PLEASE NOTE:  If the above link does not work for you, your email
application may be breaking the link into two pieces.  You may be able to
copy and paste the entire link address into the address field of your web
browser.

Referenced Items
Date            Name                             Type
----            ----                             ----
23 Feb 2004     ebBPSS-v2.0 Martins Proposa...   Minutes
26 Feb 2004     ebBP_MtgMinutes_022304.txt       Minutes