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


Help: OASIS Mailing Lists Help | MarkMail Help

wsbpel-spec-edit message

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

Subject: RE: Fw: [wsbpel-spec-edit] Done with changes mentioned in the last editors conf call

I have no problem with doing the accept-all-changes now if you want to do it Alex.  A clean copy would be nice.  We have the history in the previous versions.  And we can make a note of that in the change log in the document for the clean version.


From: Alex Yiu [mailto:alex.yiu@oracle.com]
Sent: Thursday, September 02, 2004 1:17 PM
To: Prasad Yendluri
Cc: Diane Jordan; Satish Thatte; bpel spec; Alex Yiu
Subject: Re: Fw: [wsbpel-spec-edit] Done with changes mentioned in the last editors conf call


Hi, Prasad and All,

Regarding to the copy-and-paste thing, it is a brain-dead process: "locate-copy-locate-paste-reformat". For a small delta, that is easy. But, for a big delta, it is just tedious and error prone. Maybe, when we have a big delta next time, I would ask for your help. :-)

One side question: when we will use the "Accept Changes" feature in MS Word? Some parts of the spec doc are not that easy to read now because we have accumulated enough changes. Particularly in XML content (e.g. BPEL sample code).



Prasad Yendluri wrote:


To not confuse things I will hold off on uploading a newer version until we want the team to consider this (later version for review). If you still want a newer version to go out irrespective just say so.

Hi Alex:  Hmmm, I scratching my head on this. If one does a 'cvs diff ' it shows all changes that went in the last ck-in. Is that enough for copy paste back into word? I volunteer to do it if it helps..


Diane Jordan wrote:

Hi Satish,
On the call yesterday, there was a question as to which version we want the TC to review for approval at the upcoming f2f - we thought on the call that the last one that was uploaded, http://www.oasis-open.org/apps/org/workgroup/wsbpel/download.php/8750/wsbpel-specification-draft-July-30-2004.html
is the one that includes the resolutions that were passed at the last f2f in June.  We had set as a goal inclusion of these and approval of resulting updated spec for the Sept. f2f (only 3 weeks away).

What do you think?  If it should be the later version, let me know.  I will send an email to the full TC with a reminder to start the review process.  
Regards, Diane
IBM  Emerging Internet Software Standards
(919)254-7221 or 8-444-7221, Mobile: 919-624-5123, Fax 845-491-5709

----- Forwarded by Diane Jordan/Raleigh/IBM on 09/02/2004 10:59 AM -----

"Satish Thatte" <satisht@microsoft.com>

09/02/2004 01:39 AM


"Alex Yiu" <alex.yiu@oracle.com>, "bpel spec" <wsbpel-spec-edit@lists.oasis-open.org>


"Prasad Yendluri" <pyendluri@webmethods.com>


RE: [wsbpel-spec-edit] Done with changes mentioned in the last editors conf call

I believe we should go ahead and upload a new spec draft now for the TC.  Thanks for taking that on again.

From: Alex Yiu [mailto:alex.yiu@oracle.com]
Wednesday, September 01, 2004 10:12 PM
bpel spec
Alex Yiu; Prasad Yendluri
[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:

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. :-)


Alex Yiu


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