Formated minutes of 2008-10-23 telcon

[Anish Karmarkar <Anish.Karmarkar@oracle.com>]

Attached.
Thanks to Najeeb for scribing.

-Anish
--

Title: SCA-BPEL - 2008-10-23

Hide IRC

- DRAFT -

OASIS SCA-BPEL TC telcon

23 OCT 2008

Attendees

Present

Michael Rowley, (Active Endpoints, Inc.)

Dave Booz, (IBM)

Mike Edwards, (IBM)

Dieter Koenig, (IBM)

Martin Chapman, (Oracle Corporation)

Anish Karmarkar, (Oracle Corporation)

Najeeb Andrabi, (TIBCO Software Inc.)

Danny van der Rijn, (TIBCO Software Inc.)

Chair

Anish Karmarkar

Scribe

Najeeb Andrabi

Agenda:

http://lists.oasis-open.org/archives/sca-bpel/200810/msg00027.html

---

Contents

Topics

[1]  Approval of 2008-10-16 minutes
http://lists.oasis-open.org/archives/sca-bpel/200810/msg00023.html

[2]  AI review

[3]  future concalls

[4]  Labeling conformance points

[5]  Issue 23

[6]  Issue 22 discussion.

Table of Resolutions

Table of Action Items

---

Action Items

New:

---

Resolutions

• 2008-10-23-1: 2008-10-16 minutes located at http://lists.oasis-open.org/archives/sca-bpel/200810/msg00023.html approved
• 2008-10-23-2: TC adopts the format for labeling all normative statements and for a catalog of all statements in an appendix. Example of this is at http://lists.oasis-open.org/archives/sca-assembly-testing/200810/msg00000.html
• 2008-10-23-3: issue 23 is now open
• 2008-10-23-4: issue 23 is resovled with the following proposal -- Add the following to section 3.2 "The sca-bpel:service attribute MUST NOT be specified for a partner link with a partnerRole attribute referencing a role which is the only role of a partner link type." and "The sca-bpel:reference attribute MUST NOT be specified for a partner link with a myRole attribute referencing a role which is the only role of a partner link type."

---

Minutes

Scribe: Najeeb Andrabi

<anish>

Agenda -
1. Roll Call
http://www.oasis-open.org/apps/org/workgroup/sca-bpel/members/roster.php
2. Appointment of scribe
Scribe list attached below
3. Agenda bashing
4. Approval of Oct 16, 2008 minutes
http://lists.oasis-open.org/archives/sca-bpel/200810/msg00023.html
5. Action items review
http://www.oasis-open.org/apps/org/workgroup/sca-bpel/members/action_items.php
a) AI #0021
Sanjay to follow up with Mary to post the CD docs to OASIS repository
c) AI #0049
MikeR to start a discussion amongst the editors on applying the section 2.1.1 RFC2119 model to the rest of the doc
6. Concall schedule and time change
Concall schedule is fixed to PT.
7. Labeling conformance points (homework assignment) & liaison to testing http://lists.oasis-open.org/archives/sca-bpel/200810/msg00019.html
8. Issue Discussion
a) Issue 23 - http://www.osoa.org/jira/browse/BPEL-23
Title - Additional Integrity Constraints for SCA Extensions to WS-BPEL Proposal in JIRA
b) Issue 22 - http://www.osoa.org/jira/browse/BPEL22
Title -Include mapping of interface.partnerLinkType to interface.wsdl Outline of a proposal in JIRA
c) Issue 18 - http://www.osoa.org/jira/browse/BPEL-18
TITLE - Need to rewrite the SCA-BPEL specifications with RFC-2119 keywords/statements Latest proposal: http://lists.oasis-open.org/archives/sca-bpel/200810/msg00009.html
d) Issue 12 - http://www.osoa.org/jira/browse/BPEL-12
TITLE - Long-Running Request-Response Operations
9. AOB

Approval of 2008-10-16 minutes
http://lists.oasis-open.org/archives/sca-bpel/200810/msg00023.html

Resolution: 2008-10-16 minutes located at http://lists.oasis-open.org/archives/sca-bpel/200810/msg00023.html approved

AI review

 

AI #0021 discussion

 

Everything done except the file names.

Anish:

Fix remaining issues in CD02

Anish:

close AI #0021 : remaining work to be done in CD02.

 

AI #0049 discussion.

 

AI #0049 done.

future concalls

 

Next con call time won't change, but after that we'll start with a new time. See http://lists.oasis-open.org/archives/sca-bpel/200810/msg00026.html

Labeling conformance points

 

Discussion about Labeling conformance points (homework assignment).

<anish>

http://lists.oasis-open.org/archives/sca-assembly-testing/200810/msg00000.html

Mike Edwards:

Identify each normative statement and label it.
Danny van der Rijn: +1

<anish>

u can always use things like 'is required' instead of 'must'

Dieter:

Static analysis rules in BPEL are not covered by schemas.

Martin Chapman:

Are labels different in case of different conformance targets?

Michael Rowley:

agree first on RFC2119 language then apply this scheme.

Anish:

we need to move the motion to in-corporate this scheme.

<Mike Edwards>

Mike E moves that the BPEL TC adopts the format for labelling all normative statements and for a catalog of all statements in an appendix, as shown in the example SCA Assembly Specification previously sent to the list.

<anish>

The email that contains the format for labeling is at http://lists.oasis-open.org/archives/sca-assembly-testing/200810/msg00000.html

 

Dave Booz seconds.

 

motion is approved.

Resolution: TC adopts the format for labeling all normative statements and for a catalog of all statements in an appendix. Example of this is at http://lists.oasis-open.org/archives/sca-assembly-testing/200810/msg00000.html

Issue 23

<anish>

http://www.osoa.org/jira/browse/BPEL-23

<Dieter Koenig>

PROPOSAL: Add normative constraints to chapter 3 in order to avoid contradicting (and therefore useless) partner link attribute specifications.
Add the following to section 3.2:
"The sca-bpel:multiRefFrom attribute MUST not be specified for a partner link with a myRole attribute referencing a role which is the only role of a partner link type. Furthermore, sca-bpel:multiRefFrom attribute MUST not be specified for a partner link that has the sca-bpel:service attribute."
Add the following to section 3.3:
"The sca-bpel:service attribute MUST not be specified for a partner link with a partnerRole attribute referencing a role which is the only role of a partner link type." and "The sca-bpel:reference attribute MUST not be specified for a partner link with a myRole attribute referencing a role which is the only role of a partner link type."

<Dieter Koenig>

PROPOSAL: (with uppercase NOT)
Add the following to section 3.2:
"The sca-bpel:multiRefFrom attribute MUST NOT be specified for a partner link with a myRole attribute referencing a role which is the only role of a partner link type. Furthermore, sca-bpel:multiRefFrom attribute MUST not be specified for a partner link that has the sca-bpel:service attribute."
Add the following to section 3.3:
"The sca-bpel:service attribute MUST NOT be specified for a partner link with a partnerRole attribute referencing a role which is the only role of a partner link type." and "The sca-bpel:reference attribute MUST NOT be specified for a partner link with a myRole attribute referencing a role which is the only role of a partner link type."

Anish:

moves to open issue 23

 

Michael Rowley seconds.

 

Dieter moves to open issue 23.

 

motion approved: issue 23 is open.

Resolution: issue 23 is now open

 

Dieter moves to accept the proposal with upper case NOT

 

Mike Edwards seconds.

 

Issue 23 is resolved.

Resolution: issue 23 is resovled with the following proposal -- Add the following to section 3.2 "The sca-bpel:service attribute MUST NOT be specified for a partner link with a partnerRole attribute referencing a role which is the only role of a partner link type." and "The sca-bpel:reference attribute MUST NOT be specified for a partner link with a myRole attribute referencing a role which is the only role of a partner link type."

Issue 22 discussion.

Anish:

there is not detailed proposal for it.

<anish>

Something along the lines of:
A partnerLinkType that has only one role:
The equivalent interface.wsdl will be a non-callback interface. The
interface.wsdl's 'interface' attribute will point to the same portType
as the one pointed to by
plnkartnerLinkType/plnk:role/plnkortType/@name attribute.
Note that partnerLinkType points to the portType's QNames whereas
interface.wsdl uses the URL of the form <target-NS>#wsdl.interface(...).
A partnerLinkType that has two roles:
The equivalent interface.wsdl will be a callback interface. The forward
interface will have the same portType as the one pointed to by the
partnerLinkType role whose @name attribute value matches that of the
@serviceRole attribute. The callback interface be the portType that is
not assigned to the forward interface.

Michael Rowley:

we should hold on resolving this issue till the component type side related issues are resolved.

Anish:

Component type side file issue resolution and interface.partnerLinkType issue are not related.

Michael Rowley:

we need issue to track rules on component side file.

[End of Minutes]
Formatted on 2008-10-28 at 16:15:16 GMT-7

---

Minutes formatted by Schreiber, a collection of XSLT stylesheets by Bob Freund modeled after David Booth's scribe

---

Schreiber diagnostics output

[Delete this section before publishing the minutes]

citation-detection-scribed: Line 138: Check for possible unrecognized nick 'motion approved'

statistics: Schreiber found 109 input lines

edits: Schreiber found no text-edit commands

command-scribe: Line 15: Najeeb Andrabi recognized

command-scribe: Schreiber detected that this section was scribed online

citation-detection-irc1: Line 21: Check for possible unrecognized nick 'http'

citation-detection-irc1: Line 29: Check for possible unrecognized nick 'http'

citation-detection-irc1: Line 32: Check for possible unrecognized nick 'http'

citation-detection-irc1: Line 63: Check for possible unrecognized nick 'http'

system: Transformer: SAXON 9.0.0.2

[End of Schreiber diagnostic output]