Prasad,
I believe we should go ahead and upload a
new spec draft now for the TC. Thanks for taking that on again.
Satish
From: Alex Yiu [mailto:alex.yiu@oracle.com]
Sent: Wednesday, September 01, 2004
10:12 PM
To: bpel spec
Cc: Alex Yiu; Prasad Yendluri
Subject: [wsbpel-spec-edit] Done
with changes mentioned in the last editors conf call
Hi, all editors,
I am done with changes mentioned in the last editors conf call
- Applying Issue 146: Making tVariable Extensible
- Applying Issue 149: Adding formal documentation
support to BPEL
- A bunch of misc cleanup for Issue 13
The first two items are quite easy and trivial.
For the last item, there are quite few places that remained to be finished for
Issue 13: in both MS-Word Document and XSD.
For the XSD changes, you can review it from:
http://www-124.ibm.com/developerworks/oss/cvs/wsbpeltc/specifications/SchemaFiles/wsbpel_main.xsd.diff?r2=1.9&r1=1.8&f=H
In the MS Word spec doc, you can search for "<onAlarm",
"<wait", "<expression", "<while".
If you got some time, please review the changes.
Anyhow, I can pass the pen back to the editing group.
Prasad ... regarding to keep a XSD copy in the main MS-Word doc, I am still for
this editing process. For small changes (e.g. Issue 146 and 149), manual
copying the changes piece-by-piece to the Word doc is still feasible. However,
for changes of a bigger scale (e.g. this clean up for Issue 13), it is really
quite not-so-easy, tedious and error prone. It took me more than 30 minutes to
do file-delta-merge by my hands and eyes. I think if we get another round of
bigger changes (which are quite likely given the abstract BPEL situation), then
we really should use copy and paste the whole XSD into the MS-Word doc appendix
in one shot in that case. IMHO, when delta is large, doing a
piece-by-piece delta-merging with MS-Word is not so feasible. And, MS-Word
changes-tracking feature does not apply that well to source code changes. The
final result is actually not that readable visually. [When Andrew Francis gave
us some comments months ago, he mis-read one of BPEL source code examples by
one punctuation mark because of this MS-Word changes tracking visual features.]
Just some data points for your consideration. ... :-) ... We can
discuss it further, if you wish. :-)
Thanks.
Regards,
Alex Yiu