[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: FW: AW: [sca-bpel-editors] SCA BPEL Specification Editing work items
+1
Kind Regards
DK
(Embedded image moved to file:
pic24852.jpg)IBM
Dieter K�nig IBM Deutschland Research &
Development GmbH
Senior Technical Staff Sch�naicher Str. 220 Vorsitzender des Aufsichtsrats:
Member Martin Jetter
WebSphere Process D-71032 B�blingen Gesch�ftsf�hrung: Herbert
Server Architect Kircher
(Embedded image moved (Embedded image moved to file: Sitz der Gesellschaft:
to file: pic14799.gif) pic22863.gif)Phone (office): B�blingen
Mail: (+49) 7031-16-3426
dieterkoenig@de.ibm.com
(Embedded image moved (Embedded image moved to file: Registergericht: Amtsgericht
to file: pic11454.gif) pic08322.gif)Phone (home Stuttgart, HRB 243294
WebSphere Software office): (+49) 7032-201464
From: Anish Karmarkar <Anish.Karmarkar@oracle.com>
To: Najeeb Andrabi <nandrabi@tibco.com>
Cc: sca-bpel-editors@lists.oasis-open.org
Date: 10.07.2008 03:41
Subject: Re: FW: AW: [sca-bpel-editors] SCA BPEL Specification Editing work items
The process I would like the editors to follow is:
1) Every issue resolution that is incorporated in the spec be recorded
in the revision history section.
2) For every issue resolution that makes changes to the spec:
a) a comment be added to JIRA with a pointer to the OASIS repository
document where the change was applied
b) change the status in JIRA of the issue from 'resolved' to 'applied'.
Comments?
Thanks.
-Anish
--
Najeeb Andrabi wrote:
> I have updated the revision history: resolution for BPEL-13 was already
applied. I am going to update jira to reflect the correct status.
>
> -----Original Message-----
> From: Najeeb Andrabi
> Sent: Tuesday, July 08, 2008 4:41 PM
> To: sca-bpel-editors@lists.oasis-open.org
> Cc: Anish Karmarkar
> Subject: RE: AW: [sca-bpel-editors] SCA BPEL Specification Editing work
items
>
>
> I have completed my work items; I have created revision 7 for committee
draft 01. I have made following changes:
> 1) Reverted changes to section 2.1.
> 2) Issue resolutions for BPEL-3 and BPEL-13.
>
> Resolution for issue BEPL-9 has already been applied (from revision
history). But it looks like that the target namespace for sca-bpel should
be http://docs.oasis-open.org/opencsa/sca-bpel/200801 rather than
http://docs.oasis-open.org/ns/opencsa/sca-bpel/200801;
>
> I may be completely wrong but that is what issue resolution and meeting
minutes say.
>
> Also, I am releasing the pen.
>
> Anish: Do I have to upload this version to the document repository?
>
> -- Najeeb
>
>
> -----Original Message-----
> From: Dieter Koenig1 [mailto:dieterkoenig@de.ibm.com]
> Sent: Monday, July 07, 2008 2:20 PM
> To: Najeeb Andrabi
> Cc: Anish Karmarkar; sca-bpel-editors@lists.oasis-open.org
> Subject: RE: AW: [sca-bpel-editors] SCA BPEL Specification Editing work
items
>
>
> Hi Najeeb, I don't think anybody has it, so please go ahead.
>
> Kind Regards
> DK
>
>
>
> (Embedded image moved to file:
> pic08389.jpg)IBM
>
> Dieter K�nig IBM Deutschland Research &
> Development GmbH
>
> Senior Technical Staff Sch�naicher Str. 220 Vorsitzender
des Aufsichtsrats:
> Member Martin Jetter
>
> WebSphere Process D-71032 B�blingen
Gesch�ftsf�hrung: Herbert
> Server Architect Kircher
>
> (Embedded image moved (Embedded image moved to file: Sitz der
Gesellschaft:
> to file: pic03583.gif) pic10566.gif)Phone (office): B�blingen
> Mail: (+49) 7031-16-3426
> dieterkoenig@de.ibm.com
>
> (Embedded image moved (Embedded image moved to file:
Registergericht: Amtsgericht
> to file: pic11140.gif) pic09017.gif)Phone (home Stuttgart, HRB
243294
> WebSphere Software office): (+49) 7032-201464
>
>
>
>
>
>
>
> From: "Najeeb Andrabi" <nandrabi@tibco.com>
>
> To: "Anish Karmarkar" <Anish.Karmarkar@oracle.com>, Dieter
Koenig1/Germany/IBM@IBMDE
>
> Cc: <sca-bpel-editors@lists.oasis-open.org>
>
> Date: 07.07.2008 19:02
>
> Subject: RE: AW: [sca-bpel-editors] SCA BPEL Specification Editing
work items
>
>
>
>
>
>
>
>>> Not sure why 17 was included by Najeeb. May be he meant to assign you a
>>> different issue.
>>> But as you point out, it is still open and nothing can be done about it
> at >>this point.
>
> I think I overlooked that this issue is still open.
>
> Also, is anyone holding the pen? I would like to pick it up.
>
>
> -----Original Message-----
> From: Anish Karmarkar [mailto:Anish.Karmarkar@oracle.com]
> Sent: Thursday, July 03, 2008 4:57 PM
> To: Trickovic, Ivana
> Cc: Najeeb Andrabi; sca-bpel-editors@lists.oasis-open.org
> Subject: Re: AW: [sca-bpel-editors] SCA BPEL Specification Editing work
> items
>
> Trickovic, Ivana wrote:
>> Hi all,
>>
>>
>> I checked CD01 rev 6:
>>
>> - Resolution of issue BPEL-6 was already incorporated into the document.
>>
>
> Ok. Thanks.
>
> Can the editors update JIRA to change the status of issues, whose
> resolutions are already incorporated in the document, to 'applied' ?
> The JIRA should also point to the version in the doc repository which
> includes the resolution. The revision history in the spec should also be
> updated to include the fact that the resolution was applied.
>
>> - Resolution of issue BPEL-5: A clarification is needed as the initial
>> text included in the issue description has been changed by Michael R. on
>> June 19, but the wording is different from the one suggested in the BPEL
>> 5 issue resolution. Can someone clarify this?
>>
>
> I assume the changes by MikeR that you are referring to are related to
> RFC2119. Please back-out those changes. See my previous email to Dieter.
>
> Thanks.
>
> -Anish
> --
>
>>
>> I am out of the office starting tomorrow, and will be back on July 14. I
>> am releasing the pen now. I can resume the editing when I return.
>>
>>
>>
>> Thanks,
>>
>>
>>
>> Ivana
>>
>>
>> *Ivana Trickovic*
>> Standards Architect
>> *SAP AG*
>> Dietmar-Hopp-Allee 16
>> 69190 Walldorf, Germany
>> T +49 6227 7-63228
>> F +49 6227 78-33160
>> M +49 151 57118422
>> mailto:ivana.trickovic@sap.com
>> _____www.sap.com_ <http://www.sap.com/>
>>
>> Sitz der Gesellschaft/Registered Office: Walldorf, Germany
>> Vorstand/SAP Executive Board: Henning Kagermann (Sprecher/Co-CEO), L�o
>> Apotheker (Sprecher/Co-CEO), Werner Brandt, Claus Heinrich, Gerhard
>> Oswald, John Schwarz, Peter Zencke
>>
>> Vorsitzender des Aufsichtsrats/Chairperson of the SAP Supervisory Board:
>> Hasso Plattner
>> Registergericht/Commercial Register Mannheim No HRB 350269
>>
>> Diese E-Mail kann Betriebs- oder Gesch�ftsgeheimnisse oder sonstige
>> vertrauliche Informationen enthalten. Sollten Sie diese E-Mail
>> irrt�mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts,
>> eine Vervielf�ltigung oder Weitergabe der E-Mail ausdr�cklich untersagt.
>>
>> Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail.
>> Vielen Dank.
>>
>> This e-mail may contain trade secrets or privileged, undisclosed, or
>> otherwise confidential information. If you have received this e-mail in
>> error, you are hereby notified that any review, copying, or distribution
>> of it is strictly prohibited. Please inform us immediately and destroy
>> the original transmittal. Thank you for your cooperation.
>>
>>
>>
>>
>> ------------------------------------------------------------------------
>> *Von:* Najeeb Andrabi [mailto:nandrabi@tibco.com]
>> *Gesendet:* Mittwoch, 18. Juni 2008 01:12
>> *An:* sca-bpel-editors@lists.oasis-open.org
>> *Betreff:* [sca-bpel-editors] SCA BPEL Specification Editing work items
>>
>>
>>
>> Hi All,
>>
>> I did not get any response regarding the editing
>> work. I have been assigned the task of coming up with the date when we
>> can complete this task. In order to achieve this objective I have
>> divided work equally amongst the editing team as shown below. Please let
>> me know if you would be able to work on it and how long it will take?
>>
>>
>>
>> Also, I was wondering if Michael would take up the
>> task of re-writing a section of specification in RFC2119 language;
>> Michael has already re-written section 2.1 Services and References in
>> RFC2119, he can update the section based on the conformance targets that
>> were agreed upon; Michael, would you be able to do it?
>>
>>
>>
>> Thanks,
>>
>> Najeeb
>>
>>
>>
>>
>>
>> Dieter Koenig:
>>
>>
>>
>> *T*
>>
>>
>>
>> *Key*
>>
>>
>>
>> *Summary*
>>
>>
>>
>> *Assignee*
>>
>>
>>
>> *Reporter*
>>
>>
>>
>> *Pr*
>>
>>
>>
>> *Status*
>>
>>
>>
>> *Res*
>>
>>
>>
>> *Created*
>>
>>
>>
>> *Updated*
>>
>> [Descending order - Click to sort in ascending order]
>>
>>
>>
>> *Due*
>>
>> Bug <http://www.osoa.org/jira/browse/BPEL-20>
>>
>>
>>
>> BPEL-20 <http://www.osoa.org/jira/browse/BPEL-20>
>>
>>
>>
>> SCA-BPEL spec can not require bpel:mustUnderstand to be true
>> <http://www.osoa.org/jira/browse/BPEL-20>
>>
>>
>>
>> Anish Karmarkar
>>
>>
>>
>> Michael Rowley
>>
>>
>>
>> Major
>>
>>
>>
>> ResolvedResolved
>>
>>
>>
>> UNRESOLVED
>>
>>
>>
>> 01/May/08
>>
>>
>>
>> 29/May/08
>>
>>
>>
>>
>>
>> Bug <http://www.osoa.org/jira/browse/BPEL-17>
>>
>>
>>
>> BPEL-17 <http://www.osoa.org/jira/browse/BPEL-17>
>>
>>
>>
>> Allow Component Type side file to override defaults for
>> service/reference <http://www.osoa.org/jira/browse/BPEL-17>
>>
>>
>>
>> Anish Karmarkar
>>
>>
>>
>> Alex Yiu
>>
>>
>>
>> Major
>>
>>
>>
>> OpenOpen
>>
>>
>>
>> UNRESOLVED
>>
>>
>>
>> 17/Jan/08
>>
>>
>>
>> 01/May/08
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Marin Chapman:
>>
>>
>>
>> *T*
>>
>>
>>
>> *Key*
>>
>>
>>
>> *Summary*
>>
>>
>>
>> *Assignee*
>>
>>
>>
>> *Reporter*
>>
>>
>>
>> *Pr*
>>
>>
>>
>> *Status*
>>
>>
>>
>> *Res*
>>
>>
>>
>> *Created*
>>
>>
>>
>> *Updated*
>>
>> [Descending order - Click to sort in ascending order]
>>
>>
>>
>> *Due*
>>
>> Bug <http://www.osoa.org/jira/browse/BPEL-19>
>>
>>
>>
>> BPEL-19 <http://www.osoa.org/jira/browse/BPEL-19>
>>
>>
>>
>> SCA-BPEL XML Schema <http://www.osoa.org/jira/browse/BPEL-19>
>>
>>
>>
>> Anish Karmarkar
>>
>>
>>
>> Dieter Koenig
>>
>>
>>
>> Major
>>
>>
>>
>> ResolvedResolved
>>
>>
>>
>> UNRESOLVED
>>
>>
>>
>> 13/Mar/08
>>
>>
>>
>> 17/Apr/08
>>
>>
>>
>>
>>
>> Bug <http://www.osoa.org/jira/browse/BPEL-2>
>>
>>
>>
>> BPEL-2 <http://www.osoa.org/jira/browse/BPEL-2>
>>
>>
>>
>> Does the spec allow a componentType side file
>> <http://www.osoa.org/jira/browse/BPEL-2>
>>
>>
>>
>> Sanjay Patil
>>
>>
>>
>> Alex Yiu
>>
>>
>>
>> Major
>>
>>
>>
>> ResolvedResolved
>>
>>
>>
>> UNRESOLVED
>>
>>
>>
>> 04/Oct/07
>>
>>
>>
>> 17/Apr/08
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Michael Rowley:
>>
>>
>>
>> *T*
>>
>>
>>
>> *Key*
>>
>>
>>
>> *Summary*
>>
>>
>>
>> *Assignee*
>>
>>
>>
>> *Reporter*
>>
>>
>>
>> *Pr*
>>
>>
>>
>> *Status*
>>
>>
>>
>> *Res*
>>
>>
>>
>> *Created*
>>
>>
>>
>> *Updated*
>>
>> [Descending order - Click to sort in ascending order]
>>
>>
>>
>> *Due*
>>
>> Bug <http://www.osoa.org/jira/browse/BPEL-1>
>>
>>
>>
>> BPEL-1 <http://www.osoa.org/jira/browse/BPEL-1>
>>
>>
>>
>> support for BPEL4WS 1.1 <http://www.osoa.org/jira/browse/BPEL-1>
>>
>>
>>
>> Sanjay Patil
>>
>>
>>
>> Alex Yiu
>>
>>
>>
>> Major
>>
>>
>>
>> ResolvedResolved
>>
>>
>>
>> UNRESOLVED
>>
>>
>>
>> 04/Oct/07
>>
>>
>>
>> 21/Feb/08
>>
>>
>>
>>
>>
>> Bug <http://www.osoa.org/jira/browse/BPEL-11>
>>
>>
>>
>> BPEL-11 <http://www.osoa.org/jira/browse/BPEL-11>
>>
>>
>>
>> BPEL variable initialization and SCA properties
>> <http://www.osoa.org/jira/browse/BPEL-11>
>>
>>
>>
>> Anish Karmarkar
>>
>>
>>
>> Alex Yiu
>>
>>
>>
>> Major
>>
>>
>>
>> ResolvedResolved
>>
>>
>>
>> UNRESOLVED
>>
>>
>>
>> 16/Oct/07
>>
>>
>>
>> 10/Jan/08
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Ivana Trickovic:
>>
>>
>>
>>
>>
>> *T*
>>
>>
>>
>> *Key*
>>
>>
>>
>> *Summary*
>>
>>
>>
>> *Assignee*
>>
>>
>>
>> *Reporter*
>>
>>
>>
>> *Pr*
>>
>>
>>
>> *Status*
>>
>>
>>
>> *Res*
>>
>>
>>
>> *Created*
>>
>>
>>
>> *Updated*
>>
>> [Descending order - Click to sort in ascending order]
>>
>>
>>
>> *Due*
>>
>> Bug <http://www.osoa.org/jira/browse/BPEL-5>
>>
>>
>>
>> BPEL-5 <http://www.osoa.org/jira/browse/BPEL-5>
>>
>>
>>
>> The algorithm for deciding whether a partnerLink is a service or a
>> reference needs to be deterministic
>> <http://www.osoa.org/jira/browse/BPEL-5>
>>
>>
>>
>> Sanjay Patil
>>
>>
>>
>> Alex Yiu
>>
>>
>>
>> Major
>>
>>
>>
>> ResolvedResolved
>>
>>
>>
>> UNRESOLVED
>>
>>
>>
>> 04/Oct/07
>>
>>
>>
>> 08/Nov/07
>>
>>
>>
>>
>>
>> Bug <http://www.osoa.org/jira/browse/BPEL-6>
>>
>>
>>
>> BPEL-6 <http://www.osoa.org/jira/browse/BPEL-6>
>>
>>
>>
>> Make local partnerLink aliases deterministic
>> <http://www.osoa.org/jira/browse/BPEL-6>
>>
>>
>>
>> Sanjay Patil
>>
>>
>>
>> Alex Yiu
>>
>>
>>
>> Major
>>
>>
>>
>> ResolvedResolved
>>
>>
>>
>> UNRESOLVED
>>
>>
>>
>> 04/Oct/07
>>
>>
>>
>> 25/Oct/07
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Najeeb Andrabi:
>>
>>
>>
>>
>>
>>
>>
>> *T*
>>
>>
>>
>> *Key*
>>
>>
>>
>> *Summary*
>>
>>
>>
>> *Assignee*
>>
>>
>>
>> *Reporter*
>>
>>
>>
>> *Pr*
>>
>>
>>
>> *Status*
>>
>>
>>
>> *Res*
>>
>>
>>
>> *Created*
>>
>>
>>
>> *Updated*
>>
>> [Descending order - Click to sort in ascending order]
>>
>>
>>
>> *Due*
>>
>> Bug <http://www.osoa.org/jira/browse/BPEL-3>
>>
>>
>>
>> BPEL-3 <http://www.osoa.org/jira/browse/BPEL-3>
>>
>>
>>
>> Correlation disagreement between SCA and BPEL
>> <http://www.osoa.org/jira/browse/BPEL-3>
>>
>>
>>
>> Sanjay Patil
>>
>>
>>
>> Alex Yiu
>>
>>
>>
>> Major
>>
>>
>>
>> ResolvedResolved
>>
>>
>>
>> UNRESOLVED
>>
>>
>>
>> 04/Oct/07
>>
>>
>>
>> 06/Dec/07
>>
>>
>>
>>
>>
>> Bug <http://www.osoa.org/jira/browse/BPEL-13>
>>
>>
>>
>> BPEL-13 <http://www.osoa.org/jira/browse/BPEL-13>
>>
>>
>>
>> ComponentType should not contain implementation.bpel
>> <http://www.osoa.org/jira/browse/BPEL-13>
>>
>>
>>
>> Anish Karmarkar
>>
>>
>>
>> Anish Karmarkar
>>
>>
>>
>> Major
>>
>>
>>
>> ResolvedResolved
>>
>>
>>
>> UNRESOLVED
>>
>>
>>
>> 01/Nov/07
>>
>>
>>
>> 29/Nov/07
>>
>>
>>
>>
>>
>> Bug <http://www.osoa.org/jira/browse/BPEL-9>
>>
>>
>>
>> BPEL-9 <http://www.osoa.org/jira/browse/BPEL-9>
>>
>>
>>
>> SCA-BPEL XML Namespaces <http://www.osoa.org/jira/browse/BPEL-9>
>>
>>
>>
>> Sanjay Patil
>>
>>
>>
>> Alex Yiu
>>
>>
>>
>> Major
>>
>>
>>
>> ResolvedResolved
>>
>>
>>
>> UNRESOLVED
>>
>>
>>
>> 10/Oct/07
>>
>>
>>
>> 08/Nov/07
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail. You may a link to this group and all your TCs in
> OASIS
> at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail. Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>
>
>
>
> ------------------------------------------------------------------------
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail. Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
