Hi Everyone:
I look forward to our meeting this morning at 11:00 AM. I am including the
Schedule of events just in case someone missed them. I am also attaching
What I have up to this point relative to the minutes of our last meeting. I
Have tried to be detailed so that each meeting will become a learning
Exercise. It is vital that we strive for understanding of the Abstract BPEL
Concept. This will insure that our ultimate decisions are correct.
Unfortunately For me, my time here at Unisys is not dedicated to this topic
as a result, There are several items from the last meeting which I have not yet been
Able to complete but I am working on them and will have them done for our
Next meeting.
What I have completed of the minutes from last week are
Attached along with some of my personal questions and comments. To
insure the accuracy of my reporting and to have a history
Of these meetings, I will be taping them. Hope no one objects but it is the
Only way I can coordinate and scribe and learn at the same time.
Phil
Phil Rossomando
Research Director, Technology & Architecture
Unisys Corporation
Unisys Way, B-330
Blue Bell, PA 19424 USA
Philip.rossomando@unisys.com
215-986-3998
FAX 413-0215-2043
Abstract BPEL Clarification Working Group
Members:
Our next teleconference will be on Friday 5/21/2004 from 11:00 AM to 12:00 AM
EDT.
Our ultimate objective remains to address the "left something out"
point raised by Satish in our previous meeting. What are the "some
things?" and what's left after these are left out. What is Abstract BPEL
to be used for? We need to arrive at a consensus of opinion. The key here is to
get all idea on the table. I want to personally thank all those who attended
our last meeting and if you know others who may be interested, please feel free
to invite them. The contact number is 1-877-302-3764 and the pass code is
4233998. I am looking forward to our next meeting. Please try to come prepared.
I apologize in advance if I did not include some of you on the direct
mailing list. If you would kindly send me email to this effect, I will happily
correct the omission in the future. (Ivana, sorry but I could not find your
email address L).
Action Items:
All: Try to write what you personally consider an Abstract BPEL Use
Case.
Here if you don’t write one, get behind someone who has/will so that
Your views are expressed.
All: Come up with a list of “Must Haves” relative to Abstract BPEL. This
Action is especially important for those of you who don’t write a Use
Case.
All: Understand the
point being brought out by Issues 82, 109 and 107.
Satish: Make explicit the two use cases related to abstract BPEL. The first
Relates to providing templates for those wishing to provide
implementations of standardized services. The second relates to
To define the externally visible contract for a protocol. See letter
at bottom of this email message. (Note: Nick was supposed to help
Satish).
Nick: When use cases and requirements are available figure out what is
The definition of Abstract BPEL. (Actually, this is an action item for the
Group to ultimately address.)
Alex: To resend what he created relative to Abstract and Executable BPEL
XSDs.
Phil: Contact Yaron and ask to see if he can come up with an Abstract
BPEL Use Case that incorporates opaque as both an element and an
Attribute.
Phil: Remind John to provide us with the Abstract BPEL Use Case he promised
Us for May 14 meeting.
Phil: Get out the minutes of this meeting.
Diane: Get us a place (sub-list) on our TC Web site where we can post our work products.
Left over from Last Meeting:
All: Review spec on abstract BPEL Section 15 (extensions for Business Protocols).
Although not present, it would be nice if Yaron would come up with a Use Case incorporating
Opaque as an Element and as an attribute.