Formatted minutes of 2008-02-28 telcon

Minutes

Scribe: Martin Chapman

Agenda --
1. Roll Call
http://www.oasis-open.org/apps/org/workgroup/sca-bpel/members/roster.php
2. Appointment of scribe
Rotating list attached below
3. Agenda bashing
4. Approval of Feb 21, 2008 meeting minutes
http://lists.oasis-open.org/archives/sca-bpel/200802/msg00021.html
5. Action items review
http://www.oasis-open.org/apps/org/workgroup/sca-bpel/members/action_items.php
#0021 chairs to follow up with Mary to post the CD docs to OASIS repository
#0024 Martin Chapman to write up a proposal for issue 15 (Define
Conformance Targets) http://osoa.org/jira/browse/BPEL-15
#0025 Michael Rowley to raise issue with the Assembly TC to allow for
expressing implementation type specific Service/Reference identification
and naming in the ComponentType files.
DONE
#0026 Michael Rowley to propose a partial resolution to the SCA BPEL
Issue 17 using the proposal suggested in earlier action (#0025)
DONE
#0027 Michael Rowley to update status of issue 1
6. F2F meeting in May: do we need it?
In a previous concall we decided to discuss whether we want to have a
f2f meeting or not on Feb 28th. Issue stats: Of the 7 new and open
issues -- 2 (15 & 1 are about conformance targets and RFC 2119 keywords
2 (8 & 12) are postponed 1 (17) is close to being resolved That leaves
just 2 non-conformance target/language issues + testing. The meeting is
in May. With two months to go, a f2f does not seem to be justified
(especially for folks not on the west coast). I suggest we cancel it.
7. CD 01 namespace URI
We agreed to a NS design and versioning policy document
(http://lists.oasis-open.org/archives/sca-bpel/200710/msg00050.html).
There are two things to consider:
a. the NS URI that OASIS has asked us to use contains an extra 'ns'
component. This is not what the TAB recommends. Are we ok with that? b.
the NS URI in CD 01 is:
http://docs.oasis-open.org/ns/opencsa/sca-bpel/200801 whereas the NS URI
in CD 01 of SCA Policy document is:
http://docs.oasis-open.org/ns/opencsa/sca/200712. We need to have
consistency across specs since we are sharing the NS URI.
8. New Issues
NONE
9. Issue Discussion
a) Issue 17 http://osoa.org/jira/browse/BPEL-17
TITLE: Allow Component Type side file to override defaults for
services and references
SUBMITTED BY: Anish Karmarkar
Partial resolution proposal at
http://lists.oasis-open.org/archives/sca-bpel/200802/msg00024.html
b) Issue 14 http://www.osoa.org/jira/browse/BPEL-14
TITLE: Allow sca-aware processes to specify everything that can be
specified in a CT side file
SUBMITTED BY: Anish Karmarkar
c) Issue 15 http://www.osoa.org/jira/browse/BPEL-15
TITLE: Define Conformance Targets
SUBMITTED BY: Martin Chapman
d) Issue 18 http://www.osoa.org/jira/browse/BPEL-18
TITLE: Need to rewrite the SCA-BPEL specifications with RFC-2119
keywords/statements
SUBMITTED BY: KHANDERAO KAND
e) Issue 16 http://osoa.org/jira/browse/BPEL-16
TITLE: Ambigous Service Resolution
SUBMITTED BY: Dieter Koenig
10. AOB

agenda

agenda approved

approval of minutes

http://lists.oasis-open.org/archives/sca-bpel/200802/msg00021.html

approved unanimously

AIs

#0021 chairs to follow up with Mary to post the CD docs to
OASIS repository

to be convered in agenda

#0024 Martin Chapman to write up a proposal for issue 15
(Define Conformance Targets) http://osoa.org/jira/browse/BPEL-15

ongoing

#0027 Michael Rowley to update status of issue 1

Done

F2F meeting in May: do we need it?

Anish says not many issues so many not be easy to justify a F2F.

Mike R:

agree

Danny, Deiter, agree

Mike R:

was going to do this at OASIS symposium. Editors might
want to meet then.

<Anish>

that would not be a TC meeting for voting rights

no objection to cancelling F2F in May

Action: Chairs to inform Jane about room at the Symposium

CD 01 namespace URI

The TC agreed a format based on a liaison SC document.

There is a namespace in the CD

it differs from Policy

the format in the CD includes an /ns/ token recomemneded by
OASIS Staff

Sanjay:

policy and bpel are ahead of assembly managing the
shared namespace

what is the common namespace we should use?

current contents of the cd document:
- sca http://docs.oasis-open.org/ns/opencsa/sca/200712
- sca-bpel (defined here)
http://docs.oasis-open.org/ns/opencsa/sca-bpel/200801

Martin:

liaison should coordinate the namespace name between tcs

sanjay:

what deiter pasted is fine

the bpel specific namespace doesnt have to have the same date
as the shard one

sanjay:

ask assmebly tc to finalise common namespace uri
before publishing the CD

Danny:

we just publish that we are compatible with a certain
namespace, we dont need permission

Danny:

they may give us a namespace before they formalise it.
Its a bootstrapping problem

and shouldn't occur in the future

Adopt the format
http://docs.oasis-open.org/ns/opencsa/sca-bpel/[yyyymm] for the SCA BPEL
TC defined namespace URI

Motion: Sanjay, to adopt the namespace as suggested by tc admin

2nd: martin

discussion: none

no objections, motion passes

Issues

Issue 17 http://osoa.org/jira/browse/BPEL-17
TITLE: Allow Component Type side file to override defaults for
services and references
SUBMITTED BY: Anish Karmarkar
Partial resolution proposal at
http://lists.oasis-open.org/archives/sca-bpel/200802/msg00024.html

part of it moved to assembly

Mike R goes thru msg00024

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.

Mike R:

assumes assembly will accept the proposal

<anish>

minor syntax Q: shouldn't it be: //partnerLink/[@name=$name] ?

"//partnerLink/[@name=$name]" is ambigous if there are
multiple partner links with the same name

Mike R:

an alternative is not mention xpath version as people
could be using 2.0 and it wouldnt really matter

deiter:

the xpath expression could be ambiguous

mike r:

thats ok, will result in more than one partnerlink

the last line of proposal covers this

Mike R:

Need to wait for assembly before we can resolve this

Motion: Mike R add this text to the jira for issue-17 noting
that it will be used as the resolution if assembly adopts the sca-bpel
proposal

2nd Dieter

no objections. Approved

Issue 14 http://www.osoa.org/jira/browse/BPEL-14
TITLE: Allow sca-aware processes to specify everything that can be
specified in a CT side file

Anish:

describes the issue

Perhaps @sca:serviceName="foo" or
@sca:referenceName="foo" on partnerLinks.

scribed lost the thread

but no decisions have been made

do we want to have a call in the next week given that SCA-J TC
is meeting for their F2F

meeting next week

F2f going on, so inclined to cancel

Anish:

next weeks meeting is cancelled

Adjourned

Next mtg: Mar 13

Schreiber diagnostics output

[Delete this section before publishing the minutes]

final validation: Title not specified, default title 'OASIS SCA-BPEL TC...' was assumed

citation-detection-scribed: Line 195: Check for possible unrecognized nick 'Motion'

citation-detection-scribed: Line 197: Check for possible unrecognized nick '2nd'

citation-detection-scribed: Line 199: Check for possible unrecognized nick 'discussion'

citation-detection-scribed: Line 243: Check for possible unrecognized nick 'Motion'

statistics: Schreiber found 182 input lines

edits: Schreiber found no text-edit commands

command-scribe: Line 5: Martin Chapman 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 68: Check for possible unrecognized nick 'http'

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

citation-detection-irc1: Line 79: Check for possible unrecognized nick 'a) Issue 17 http'

citation-detection-irc1: Line 80: Check for possible unrecognized nick 'TITLE'

citation-detection-irc1: Line 82: Check for possible unrecognized nick 'SUBMITTED BY'

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

citation-detection-irc1: Line 86: Check for possible unrecognized nick 'b) Issue 14 http'

citation-detection-irc1: Line 87: Check for possible unrecognized nick 'TITLE'

citation-detection-irc1: Line 89: Check for possible unrecognized nick 'SUBMITTED BY'

citation-detection-irc1: Line 91: Check for possible unrecognized nick 'c) Issue 15 http'

citation-detection-irc1: Line 92: Check for possible unrecognized nick 'TITLE'

citation-detection-irc1: Line 93: Check for possible unrecognized nick 'SUBMITTED BY'

citation-detection-irc1: Line 95: Check for possible unrecognized nick 'd) Issue 18 http'

citation-detection-irc1: Line 96: Check for possible unrecognized nick 'TITLE'

citation-detection-irc1: Line 98: Check for possible unrecognized nick 'SUBMITTED BY'

citation-detection-irc1: Line 100: Check for possible unrecognized nick 'e) Issue 16 http'

citation-detection-irc1: Line 101: Check for possible unrecognized nick 'TITLE'

citation-detection-irc1: Line 102: Check for possible unrecognized nick 'SUBMITTED BY'

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

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

citation-detection-irc1: Line 206: Check for possible unrecognized nick 'TITLE'

citation-detection-irc1: Line 208: Check for possible unrecognized nick 'SUBMITTED BY'

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

citation-detection-irc1: Line 252: Check for possible unrecognized nick 'TITLE'

system: Transformer: SAXON 9.0.0.2

[End of Schreiber diagnostic output]

sca-bpel message

- DRAFT -

OASIS SCA-BPEL TC

28 FEB 2008

Attendees

Contents

Action Items

Resolutions

Minutes

agenda

approval of minutes

AIs

F2F meeting in May: do we need it?

CD 01 namespace URI

Issues

meeting next week

Schreiber diagnostics output