Formatted minutes of 2008-07-10 telcon

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

Attached.
Thanks to Khanderao for scribing.

-Anish
--

Title: SCA-BPEL - 2008-07-10

Hide IRC

- DRAFT -

OASIS SCA-BPEL TC telcon

10 JUL 2008

Attendees

Present

Mike Rowley, (Active Endpoints, Inc.)

David Booz, (IBM)

Dieter Koenig, (IBM)

Martin Chapman (Oracle Corporation)

Khanderao Kand, (Oracle Corporation)

Anish Karmarkar, (Oracle Corporation)

Ashok Malhotra, (Oracle Corporation)

Najeeb Andrabi, (TIBCO Software Inc.)

Danny van der Rijn, (TIBCO Software Inc.)

Chair

Anish Karmarkar

Scribe

Khanderao Kand

Agenda:

http://lists.oasis-open.org/archives/sca-bpel/200807/msg00004.html

---

Contents

Topics

[1]  Approval of Jun 19th Minutes:
http://lists.oasis-open.org/archives/sca-bpel/200806/msg00003.html.

[2]  Approval of Jun 26th Minutes:
http://lists.oasis-open.org/archives/sca-bpel/200806/msg00008.html.

[3]  AI review

[4]  SCA J TC's request to swap call times with us
http://lists.oasis-open.org/archives/sca-bpel/200807/msg00000.html

[5]  Discussions on new issues:

[6]  Status of spec - Update from the editors

[7]  issue 17

Table of Resolutions

Table of Action Items

---

Action Items

New:

2008-07-10-1: To Anish/chair to get back SCA-J TC to informour inability to swap the times

2008-07-10-2: Dieter to fix all the typos/errors in SCA BPEL XML schema

2008-07-10-3: Editors to updates specs(Agenda 9) by Jul 23rd 2008call.

2008-07-10-4: To all: Email your availabilities in the month of Aug. to Anish

---

Resolutions

• 2008-07-10-1: June 19, 2008 minutes located at http://lists.oasis-open.org/archives/sca-bpel/200806/msg00003.html approved
• 2008-07-10-2: June 26, 2008 minutes located at http://lists.oasis-open.org/archives/sca-bpel/200806/msg00008.html approved
• 2008-07-10-3: Jul 17, 2008 call is canceled
• 2008-07-10-4: Issue 17 closed with above resolution.

---

Minutes

<anish>

Agenda -

<anish>

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 June 19, 2008 minutes
http://lists.oasis-open.org/archives/sca-bpel/200806/msg00003.html
5. Approval of June 26, 2008 minutes
http://lists.oasis-open.org/archives/sca-bpel/200806/msg00008.html
6. Action items review
http://www.oasis-open.org/apps/org/workgroup/sca-bpel/members/action_items.php
a) AI #0021
Chairs - to follow up with Mary to post the CD docs to OASIS repository
b) AI #0042
Editors to incorporate all issue resolutions by 10 july 2008
7. SCA J TC's request to swap call times with us
http://lists.oasis-open.org/archives/sca-bpel/200807/msg00000.html
8. New Issues
a. Issues with BPEL extension schema: is reference NCName or QName and
two conflicting definitions of reference. Is this a new issue or a typo?
http://lists.oasis-open.org/archives/sca-bpel-editors/200807/msg00001.html
9. Status of spec
Update from the editors
10. Issue 17 http://www.osoa.org/jira/browse/BPEL-17
TITLE - Allow Component Type side file to override defaults for
service/reference
This issue was waiting on Assembly-52, which was recently closed with no
action.
There is a proposal to resolve this issue in JIRA.
11. Issue 18 http://www.osoa.org/jira/browse/BPEL-18
TITLE- Need to rewrite the SCA-BPEL specifications with RFC-2119
keywords/statements
See proposal (rev 5) from MikeR at
http://lists.oasis-open.org/archives/sca-bpel/200806/msg00002.html
12. AOB

Scribe: Khanderao Kand

Approval of Jun 19th Minutes:
http://lists.oasis-open.org/archives/sca-bpel/200806/msg00003.html.

 

Approved

Resolution: June 19, 2008 minutes located at http://lists.oasis-open.org/archives/sca-bpel/200806/msg00003.html approved

Approval of Jun 26th Minutes:
http://lists.oasis-open.org/archives/sca-bpel/200806/msg00008.html.

 

Approved

Resolution: June 26, 2008 minutes located at http://lists.oasis-open.org/archives/sca-bpel/200806/msg00008.html approved

AI review

 

a) AI #0021
Chairs - to follow up with Mary to post the CD docs to OASIS repository.

<Mike Edwards>

she has had the Assembly CD-01 for nearly 5 months

 

Mary's task list is full. No ETA from Mary. AI pending.

 

Updated on AI b) AI #0042
Editors to incorporate all issue resolutions by 10 july 2008: Pending

SCA J TC's request to swap call times with us
http://lists.oasis-open.org/archives/sca-bpel/200807/msg00000.html

 

Dieter won't be able regularly with the proposed time.

 

No supporter to change the time.

Action: To Anish/chair to get back SCA-J TC to informour inability to swap the times

Discussions on new issues:

 

a. Issues with BPEL extension schema: is reference NCName or
QName and two conflicting definitions of reference. Is this a new issue
or a typo?
http://lists.oasis-open.org/archives/sca-bpel-editors/200807/msg00001.html

Dieter:

It is a typo. Easily fixable and can be treated as an
Action Item as against a new issue.

Action: Dieter to fix all the typos/errors in SCA BPEL XML schema

 

Other aspect is inconsistency of name space prefix . Dieter
ready to volunteer to fix.

Status of spec - Update from the editors

 

Najib informed that he is done with his changes.

 

Dieter got the pen now.

 

Martin moved a motion to cancel the next call on Jul 17th 2008. Second: Danny

 

No discussion. No Objections. Motion passed unanimously

Resolution: Jul 17, 2008 call is canceled

Action: Editors to updates specs(Agenda 9) by Jul 23rd 2008call.

 

Discussions on LOAs in August.

Action: To all: Email your availabilities in the month of Aug. to Anish

issue 17

<anish>

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

 

Discussion on Agenda item 10. Issue 17
http://www.osoa.org/jira/browse/BPEL-17
TITLE - Allow Component Type side file to override defaults for
service/reference
This issue was waiting on Assembly-52, which was recently closed with no
action.
There is a proposal to resolve this issue in JIRA.

<Mike Edwards>

helpful people, these Assembly folks

 

Assembly-52 was closed by the SCA Assembly TC with no action

<Mike Edwards>

why wasn't the name constructed using the Scope name?

<Mike Edwards>

ah - scratch that comment of mine

 

MikeR updates On the SCA-BPEL TC call of 2008-02-28 we
resolved that the following text will be used as the resolution of this
issue, if the SCA Assembly specification adopts the @implementationRef
attribute that has been proposed:
The @implementationRef attribute MUST contain a valid XPath 1.0
expression, which when executed on a BPEL process returns exactly one
<partnerLink> element. The partnerLink thus identified will be
considered to correspond to the service or reference that contained the
@implementationRef attribute. If a service or reference does not have an
@implementationRef attribute, then it will act as if it had
@implementationRef=//partnerLink[@name=$name], where $name is the value
of the @name attribute of that service or reference.

MikeR:

Open question : whether to use new prefix for this new
implementationRef attribute?

Anish:

This attribute meant to be sca-bpel extension or bpel
extension.

MikeR:

This is in componentType file and no extensions over
there.

Dieter:

Confirmed.

Anish:

For scdl and component type file there is one name
space. For BPEL, it is bpel extensions.

 

The idea of creating a separate schema for one attribute is
not appropriate.

Najeeb:

we can create a new schema file and import the
existing namespace.

Anish:

There is no one good way now. We should have a
separate namespace for implementation.bpel

 

However, we do not need another discussion on single
namespace for implementation.bpel

 

MikeR and Anish preferred to put in sca-bpel namespace.

Dieter:

We should not be creating complicated dependencies.

 

Motion:by MikeR:

<anish>

existing proposal:

<anish>

The @implementationRef attribute MUST contain a valid XPath 1.0
expression, which when executed on a BPEL process returns exactly one
<partnerLink> element. The partnerLink thus identified will be
considered to correspond to the service or reference that contained the
@implementationRef attribute. If a service or reference does not have an
@implementationRef attribute, then it will act as if it had
@implementationRef=//partnerLink[@name=$name], where $name is the value
of the @name attribute of that service or reference.

<Michael Rowley>

Proposed issue resolution: An
@sca-bpel:implementationRef attribute on a component type's service or
reference MUST contain a valid XPath 1.0 expression, which when executed
on a BPEL process returns exactly one <partnerLink> element. The
partnerLink thus identified will be considered to correspond to the
service or reference that contained the @sca-bpel:implementationRef
attribute. If a service or reference does not have an
@sca-bpel:implementationRef attribute, then it will act as if it had
@sca-bpel:implementationRef=//partnerLink[@name=$name], where $name is
the value of the @name attribute of that service or reference.

 

Seconded by Danny

 

Motion passed unanimously

Resolution: Issue 17 closed with above resolution.

 

Meeting adjourned.

[End of Minutes]
Formatted on 2008-07-23 at 18:40:23 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 205: Check for possible unrecognized nick 'Motion'

statistics: Schreiber found 161 input lines

edits: Schreiber found no text-edit commands

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

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 36: Check for possible unrecognized nick 'http'

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

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

citation-detection-irc1: Line 54: Check for possible unrecognized nick '10. Issue 17 http'

citation-detection-irc1: Line 62: Check for possible unrecognized nick '11. Issue 18 http'

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

command-scribe: Line 71: Khanderao Kand recognized

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

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

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

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

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

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

system: Transformer: SAXON 9.0.0.2

[End of Schreiber diagnostic output]