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: [wsbpel-spec-edit] notes from Oct 25 call


Thanks Alex, I will contact you if I have questions.
 
regards,
-Vinky


From: Alex Yiu [mailto:alex.yiu@oracle.com]
Sent: Tuesday, October 25, 2005 4:01 PM
To: Diane Jordan
Cc: wsbpel-spec-edit@lists.oasis-open.org; Alex Yiu
Subject: Re: [wsbpel-spec-edit] notes from Oct 25 call


Hi all,

Just want to remind people that I sign up for Issue 6.2 as well.

*** Paco and Vinky,
Another reminder: the part (b) and (c) of Issue 125 are actual amendments applicable to issue 157. I guess it may be better for Vinkey to apply those two parts.

Vinky, if the resolutions of Issue 157 and parts of 125 are not clear to you, please let me know. I will be more than happy to answer questions. :-)

Thanks!


Regards,
Alex Yiu



Diane Jordan wrote:

Attendees:  Vinky, Alex, Assaf, Paco
I will review recent email and get Peter info on those issues that have been added to the spec already (92.x and possibly others).
Following is the list of assignments in order:  
  1. Paco will do 88, 174, 125, 219.  Target completion by Mon.
  2. Vinky will do 157, 222, 224, 225.  Target completion by next Fri.
  3. Assaf will complete 209, 214. Target completion by next call.
As usual we'll use email to notify the next person in the queue that the pen is free.  
Alex will start work on a resolution to 82.1 to help get conclusion on the abstract related issues.  
We discussed prognosis for completion of the spec and the likely need for a "corrective editing cycle" to address consistency and readability once all the issue resolutions are incorporated into the spec.  After all outstanding issues are resolved, we should probably plan for 4-8 weeks to incorporate them into the spec, get approval of the updated spec as the latest committee draft with all normative changes and then start the corrective editing.  Given our current status, this could happen in the Mar-April timeframe.  Some ideas for this process:  
  • get the editing team together for a multi-day session to go through the doc might be a way to get this done quickly if folks can dedicate the time.    
  • having a primary editor for the doc as a whole is the best way to get consistency especially on style, but since the doc is so large, we may want to split it into sections and appoint a primary editor and associated review team for each.
  • terminology is not used consistently - we should establish definitions and usage for words throughout

Let me know if I missed anything.  
Regards, Diane
IBM  Emerging Internet Software Standards
drj@us.ibm.com
(919)254-7221 or 8-444-7221, Mobile: 919-624-5123, Fax 845-491-5709



This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law.  If you are not the intended recipient, you should delete this message. 

Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. [v.E.1]


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