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] Summary of call today


Actually all the diagrams are not present in the word version. They are in the HTML directory (have always been IIRC). The word version never had them inline (since the very first version (1.1) we checked in). I have been manually updating the URLs in the HTML version I generated.

>In the examples, we could probably skip the standard namespace decls
>(replace with ... perhaps). What do you think?

That would be easier from maintenance perspective but, it would be nice and useful for people to see
these fleshed out in the examples IMO. Having it in the front helps in making sure all references use the
same values whenever feasible.

Regards, Prasad

-------- Original Message --------
Subject: RE: [wsbpel-spec-edit] Summary of call today
Date: Tue, 16 Mar 2004 20:25:28 +0100
From: Liu, Kevin <kevin.liu@sap.com>
To: 'Satish Thatte' <satisht@microsoft.com>, wsbpel-spec-edit@lists.oasis-open.org
CC: Alex Yiu <alex.yiu@oracle.com>

I have checked in new draft with a list of namespaces prefixes and corresponding URIs 
added to section 2 of "Notational Conventions". That should fulfill my AI number 2.

A side note: I understand that the motivation for creating the above list is to save 
some editor work when we change the namespace uris for bpws. but while searching 
through the spec to decide what prefix to list, I figure out that the list of 
prefix only helps when they are used in code snippets where namespace declaration 
is skipped. For most of our example code, there is a namespace declaration 
(eg. <definition... Xmlns:xxx="http:..." ..>). So we will still need to change 
all the places when we change the targetnamespaces for bpws. The save is limited. 

In addition, I notice that a few more editorial changes need to be made before we 
release it to the public site:

1. The following section needs to be either removed or filled in:
{FirstName} {Last Name}, {Organization}

I did put a notes there a while ago suggesting that this section should be 
consolidated with Appendix H (add some wording to H to recognize the contribution 
from all members of the TC), but we never got a chance to talk about it in our meetings. 

2. the diagram in appendix C is missing.

Best Regards,

-----Original Message-----
From: Satish Thatte [mailto:satisht@microsoft.com] 
Sent: Tuesday, Mar 16, 2004 10:24 AM
To: Liu, Kevin; wsbpel-spec-edit@lists.oasis-open.org
Cc: Alex Yiu
Subject: RE: [wsbpel-spec-edit] Summary of call today


Many thanks for doing a thorough job on AI 1.  We should add the problem
Prasad flagged for fixing faultVariable examples (incomplete fix for 68
-- my fault).

Prasad had the pen and has handed it in.  Please go ahead with your AI


-----Original Message-----
From: Liu, Kevin [mailto:kevin.liu@sap.com] 
Sent: Tuesday, March 16, 2004 10:19 AM
To: Satish Thatte; wsbpel-spec-edit@lists.oasis-open.org
Cc: Alex Yiu
Subject: RE: [wsbpel-spec-edit] Summary of call today

Two things:

1. I took an AI to look through the issue list and see if any resolved
issues need to be incorporated into the spec. I compared the revision
history and issue list. Below is my findings. 

The following issues have been resolved and incorporated into the spec
according to the revision history: 3, 7, 13, 23, 27, 32, 36, 39, 41, 46,
50, 67, 68, 70, 72, 73, 74, 79, 80, 85, 95

The following issues have been resolved and marked "closed with no
change to the spec": 5, 14, 16, 17, 18, 19, 20, 21, 22, 35, 38, 40, 42,
47, 60, 61, 69, 77

The following issues have been closed and marked as duplicates: 49, 76

>>>>>The following issues have been resolved, but seems NOT reflected in
the spec(They not included in the revision history):
- Issue 24 (separate schema for executable vs abstract BPEL): need to
assign an AI to create the two schemas as proposed

- Issue 45 (wording of "while" activity): a simple fix, but need an
editor to make the change and check if other parts of the spec will be

- Issue 62 (Event handlers and serilizable scope): need an editor to
make the change and check if other parts of the spec will be effected

- Issue 69 (when to clear link status: need an editor to make the change
and check if other parts of the spec will be effected

This should fulfill my first AI.

2. My second AI is to create the list of namespace prefixes used in the

I need a favor from whoever currently has the pen - please let me know
when you are done. I will try my best to get it done tonight. But since
I am not sure when the pen will be ready for me, and I will be traveling
this afternoon, it's at risk that this item might not be completed
before tomorrow's call. 

Best Regards,

-----Original Message-----
From: Satish Thatte [mailto:satisht@microsoft.com] 
Sent: Wednesday, Mar 10, 2004 02:49 PM
To: wsbpel-spec-edit@lists.oasis-open.org
Cc: Alex Yiu
Subject: [wsbpel-spec-edit] Summary of call today.

Alex, welcome!  Let me know that you got this message through the
mailing list channel so I can stop copying you explicitly.

Summary of the decisions and discussion today.

Ben and Paco will coordinate fixing both the language for 72 and the
schema for 74.  They will try to finish by EOD Thursday (tomorrow).

Prasad then gets the pen to incorporate the resolutions for 80 and 95.
Prasad, can you finish this by the weekend?

Kevin then gets the pen to add a set of standard namespace prefixes for
the entire spec.  Kevin, please try to finish and checkin, as well as
send the doc you check in to the TC before the next call (Diane can do a
PDF version following that if need be).

We agreed that it is a good idea to separate the schemas from the spec,
and leave just links to the schemas in the spec.  Need a TC resolution
to make this happen.  I will post the motion.

We agreed that each committee draft of the spec should have a distinct
corresponding namespace.  Using standard prefixes and not using explicit
namespace declarations in the spec examples will help with this.
However this is a significant initial effort to change the examples once
Kevin checks in the standard prefixes.  *Need a volunteer for that.*

We would like to get all this done before the next F2F and all the
substantive changes (i.e., everything except the namespace cleanup) done
before the next TC call on 3/17.


-----Original Message-----
From: Alex Yiu [mailto:alex.yiu@oracle.com] 
Sent: Wednesday, March 10, 2004 11:44 AM
To: Satish Thatte
Cc: wsbpel-spec-edit@lists.oasis-open.org; ALEX.YIU@oracle.com
Subject: Re: Agenda for tomorrow

Hi, Satish and all others,

Satish ... Thanks for inviting me! :-)
And, I missed this particular conf call. Really sorry about that.

I will attend the next conf call (March 24).

Looking forward to contributing to the spec editing, after warming up 
and learning the process and logistics arrangement of spec editing. :-)

Alex Yiu

Satish Thatte wrote:

>I made a pass over the latest draft checked in some minor changes --
the biggest one is a change to Kartha's update to comform the usual
separation of standard faults into the executable extensions section.
>Kevin, your updates were showing in the wrong font -- I fixed it.
>Made other minor corrections.
>The schema changes for 74 need help.  The maxOccurs for sources/targets
should be 1 (I changed it).  But the schemas for targets and sources
need review -- among other things they are not conforming to the element
form for joinCondition.
>We need to discuss how to incorporate the resolution of 72.  Ben has
already commented that some of the text does not belong.
>We have resolutions of 80 and 95 to incorporate.
>We need to get done and upload a draft to the OASIS site by the next TC
call so we can vote on adopting it as the next draft at the F2F.
>I have invited Alex Yiu to join the editing group since he has been
working on the schemas and has offered to help us with that and other

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