[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsbpel-abstract] Re: Regarding the summary of your report for AbsBPEL
A glossary is an essential deliverable of this TC. We need one just To understand each other. I agree with Nick and believe that I Made the same comment (i.e., a protocol is not what Abstract BPEL represents.)
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
-----Original Message-----
Nick Two points: at the F2F presumably everyone will hammer out a definition that represents a concensus. In that definition a more precise use of words needs to be reflected. I have long advocated for a glossary. Given the diversity of people on the TC and the intended audience for the spec I do not think it is realistic to assume everyone uses words the same way.
And in agreeing on a definition for abstract bpel I hope consideration will be given to using cross-over words so the definition has resonance beyond the technical community, ideally also in the business community. Conveying intent is not going to be easy, but having that definition will communicate and bound the TC's effort. Sally
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]