OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsbpel message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [wsbpel] RE: Requirements and Scope Document



As discussed on our last TC call, the original bpel4ws authors have agreed to produce a document to define the goals and discuss the rationale for the spec.  This should help with many of these questions.  We checked on status this week  - while there is some hope that a draft will be available in the next couple weeks, due to vacations there is some unpredictability, and it is possible it will take until early August.  
Regards, Diane
IBM  Dynamic e-business Technologies
drj@us.ibm.com
(919)254-7221 or 8-444-7221, Mobile: 919-624-5123



debra.kellington@convergys.com

06/30/2003 01:12 PM

       
        To:        Steve <steve@enigmatec.net>
        cc:        "Assaf Arkin" <arkin@intalio.com>, Diane Jordan/Raleigh/IBM@IBMUS, "David RR Webber - XML ebusiness" <Gnosis_@compuserve.com>, "James Bryce Clark" <jamie.clark@oasis-open.org>, "John Evdemon" <jevdemon@microsoft.com>, saskary@nuperus.com, wsbpel@lists.oasis-open.org, "Yaron Y. Goland" <ygoland@bea.com>
        Subject:        Re: [wsbpel] RE: Requirements and Scope Documents?




Knowing scope and requirements is important in any project.  How do you
know you've met your project goals without these?  Does form follow
function, or function follow form?  I think it is important to let the
documented needs drive the results.

Thanks,

Debra Kellington
Senior Manager
Convergys
(513)723-7311


                                                                                                                                     
                     Steve                                                                                                            
                     <steve@enigmatec.        To:       "Yaron Y. Goland" <ygoland@bea.com>                                          
                     net>                     cc:       "Assaf Arkin" <arkin@intalio.com>, "John Evdemon" <jevdemon@microsoft.com>,  
                                               "David RR Webber - XML ebusiness" <Gnosis_@compuserve.com>, "Diane Jordan"            
                     06/30/2003 04:39          <drj@us.ibm.com>, <saskary@nuperus.com>, <wsbpel@lists.oasis-open.org>, "James Bryce  
                     AM                        Clark" <jamie.clark@oasis-open.org>                                                    
                                              Subject:  Re: [wsbpel] RE: Requirements and Scope Documents?                            
                                                                                                                                     




+1 from me to.

All the discussions on scope and focus from me are entirely as a
consequence of not knowing the requirements that led to the development
of BPEL. Further confusion is added, as opposed to clarity, through the
BPEL authors comments on what issues remain with BPELV1.1.

I'd really like to put this whole thing to bed with a clear concise
statement so that I too can focus on the right things in the right way
and so remain at a high degree of efficiency.

If there is anything I can do, then I am a willing participant.

Cheers

Steve T

On Friday, June 27, 2003, at 05:57  pm, Yaron Y. Goland wrote:


> +1
>
>> -----Original Message-----
>> From: Assaf Arkin [mailto:arkin@intalio.com]
>> Sent: Wednesday, June 25, 2003 8:56 AM
>> To: John Evdemon
>> Cc: David RR Webber - XML ebusiness; Diane Jordan;
>> saskary@nuperus.com;
>> wsbpel@lists.oasis-open.org; James Bryce Clark; Yaron Y. Goland
>> Subject: Re: [wsbpel] RE: Requirements and Scope Documents?
>>
>>
>> John Evdemon wrote:
>>
>>> We're working with an established spec.  I'm (once again) not sure
>>> why
>>> we need to write a requirements document for an established spec.
>>>
>>>
>> We do have an established spec and it is a waste of time to
>> reverse-engineer the requirements that led to this spec just for the
>> purpose of having them written down.
>>
>> But, the TC consists of around a hundred members who have joined in
>> order to contribute to the development of the spec. We can't expect
>> people to participate and contribute if they do not all have an
>> understanding of what the spec is about. The recent discussion about
>> execution vs modeling vs authoring stems from that simple fact.
>>
>> Should I spend my employeer's time contributing ideas to improve the
>> usefulness of the spec to address XML authoring if that was never a
>> requirement? Should Edwin contribute an example for using coordination
>> protocols if that is not a requirement? And so forth.
>>
>> The authors made a conscious decision to target the spec to solve a
>> particular set of requirements. And given that we are working on an
>> established spec, I believe that for the most part we have well
>> defined
>> requirements. Some of them are implicit and well understood. Other are
>> not. If the TC is to make any forward progress it need to consider
>> clearly specifying some of these requirements so they are understood
>> to
>> the larger group.
>>
>> arkin
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: wsbpel-unsubscribe@lists.oasis-open.org
>> For additional commands, e-mail: wsbpel-help@lists.oasis-open.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wsbpel-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: wsbpel-help@lists.oasis-open.org
>
> This email is confidential and may be protected by legal privilege. If
> you are not the intended recipient,  please do not copy or disclose
> its content but  delete the email and contact the sender immediately.
> Whilst we run antivirus software on all internet emails we are not
> liable for any loss or damage. The recipient is advised to run their
> own antivirus software.
>

This email is confidential and may be protected by legal privilege. If you
are not the intended recipient,  please do not copy or disclose its content
but  delete the email and contact the sender immediately. Whilst we run
antivirus software on all internet emails we are not liable for any loss or
damage. The recipient is advised to run their own antivirus software.


---------------------------------------------------------------------
To unsubscribe, e-mail: wsbpel-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: wsbpel-help@lists.oasis-open.org





--
"NOTICE:  The information contained in this electronic mail transmission is
intended by Convergys Corporation for the use of the named individual or
entity to which it is directed and may contain information that is
privileged or otherwise confidential.  If you have received this electronic
mail transmission in error, please delete it from your system without
copying or forwarding it, and notify the sender of the error by reply email
or by telephone (collect), so that the sender's address records can be
corrected."






[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]